This document provides recommendations for performance tuning of IBM Connections 4 Connections based on the experience of the IBM Collaboration Solutions Performance team. However, the optimal tuning and the resulting system capacity can be affected by many factors, including the characteristics of the load on the system and the hardware used, including servers, disk subsystems, network topology, and more. Therefore the recommendations in this document should not be considered the optimal values for every situation, but rather a recommended starting point for tuning a Connections deployment. Using this configuration as a baseline, we suggest monitoring the system performance, making any desired changes, and measuring their impact.
via IBM Connections wiki : Tuning for Performance : IBM Connections 4.0 Performance Tuning Guide.
Open Mic Webcast replay: WebSphere Portal Performance Tuning and Troubleshooting – 26 June 2012 [slides & audio & summary attached]
via IBM Open Mic Webcast replay: WebSphere Portal Performance Tuning and Troubleshooting – 26 June 2012 [slides & audio & summary attached] – United States.
It’s a lost art, but once you try it, the better you get.
IBM Lotus® Domino® 8.5.3 and IBM Lotus Notes® 8.5.3 have been optimized to reduce the transactions from the client to the server. These optimizations yield a reduction in server resources, thus lowering the Total Cost of Ownership. This white paper shows the reductions in processor and disk utilization achieved with large numbers of Notes 8.5.3 clients running on a single Domino 8.5.3 server.
In this white paper
- N85mail and N853mail workloads defined
- Test configurations
- AIX test results
- Linux on System z results
- Appendix: Explanation of Lotus Notes.ini settings
via IBM Lotus Domino 8.5.3 server performance: IBM Lotus Notes 8.5.3 performance.
This document provides recommendations for performance tuning of IBM® Lotus® Connections 3 (Connections) based on the experience of the IBM Collaboration Solutions Performance team. However, the optimal tuning and the resulting system capacity can be affected by many factors, including the characteristics of the load on the system and the hardware used, including servers, disk subsystems, network topology, and more. Therefore the recommendations in this document should not be considered the optimal values for every situation, but rather a recommended starting point for tuning a Connections deployment. Using this configuration as a baseline, we suggest monitoring the system performance, making any desired changes, and measuring their impact.
via IBM Lotus Connections 3.0 Performance Tuning Guide.
I ran across this tip today in one of our IBM user forums and thought you all would find it interesting for increasing performance at the desktop level …
Speeding Up Notes and Symphony
Making Notes 8.x (including 8.5 beta) in Eclipse feel much faster.
I’ve been reminded of this gem, given to me by skilled person I trust, which really speeds up the way Notes 8.x in Eclipse feels. I can’t say if its actually faster, but it does feel much faster. Use your file explorer to find this directory:
for Notes version 8.5.1 The file “jvm.properties” is now located in a new place.
For versions prior to 8.5.1 –
In this folder, look for the file “jvm.properties” One of the first lines that isn’t commented out (preceeded by #) is:
Change that line to roughly half of your available ram. The recommendation I was given was actually 768, but since I have 3gb of RAM available to XP I set mine up a bit higher.
Note: Make sure you close Notes before you do this, and that all the Notes processes are terminated. If you’re not sure, reboot first. Go ahead, try it, and report what you think.
C:\Program Files (x86)\IBM\Lotus\Symphony\framework\rcp\eclipse\plugins\com.ibm.rcp.j2se.win32.x86_188.8.131.5200225b-201009231900
Just a thought in case you are interested.
IBM will host an Open Mic Webcast with Lotus Development and Support Engineers on 26 April 2011. The topic will be “Best Practices and Performance Tuning for IBM Lotus Sametime Meetings.”
Mark your calendar
Date: 26 April 2011
Time: 11:00 AM EDT (15:00 UTC), for 60 minutes
via IBM Open Mic Webcast: Best Practices and Performance Tuning for IBM Lotus Sametime Meetings – 26 April 2011 – United States.
This document is intended as a guide for resolving performance problems you may encounter with IBM WebSphere Portal version 5.1 or later. In this guide, you will find:
o Information on how to isolate the nature of the problem you are encountering
o Useful information to help you diagnose the problem
o Descriptions of common performance problems, so you can identify the specific problem you are facing, and
o Descriptions of how to resolve those problems.
This guide is intended for a technical audience – those who are comfortable working with WebSphere Portal and its associated software. It will not be generally useful to end-users who are accessing web sites built using WebSphere Portal.
This guide is not intended as the only definitive resource regarding WebSphere Portal or Java tuning, performance or troubleshooting. It provides a guideline and suggestions that will aid the majority of WebSphere Portal administrators when encountering the performance problems described in this guide. It should be used in conjunction with the product support documentation in addition to other references.
This document contains screenshots and sample log output from WebSphere Portal 6.1, running on WebSphere Application Server 184.108.40.206. Are you using a different version of WebSphere Portal? That’s not a problem. While the exact steps for some of the actions vary from version to version, the basic methodology described here applies to all versions of WebSphere Portal, and to products built on top of WebSphere Portal, such as Lotus Quickr.
via IBM – IBM WebSphere Portal Performance Troubleshooting Guide.
Tuning a WebSphere Portal environment involves tuning and configuring the various systems and components of the environment. This chapter discusses some general concepts and details the specifics of the configurations used in our measurement environments. These specifics entail:
* configuring the application server and the resources defined for that application server
* determining the cloning strategy for expanding or extending the environment
* tuning the database(s) and database server
* tuning the directory server and its database
* tuning the web server
* tuning the operating system and network
* tuning the WebSphere Portal services
When tuning your individual systems, it is important to begin with a baseline, monitor the performance metrics to determine if any parameters should be changed and, when a change is made, monitor the performance metrics to determine the effectiveness of the change.
via IBM – IBM WebSphere Portal Version 6.0 Tuning Guide.
What was done to improve the performance of the Lotus Notes client from 8.0.1 to 8.0.2 and 8.5, and what were the results?
The Notes 8 client is a highly integrated application built on an open framework. The software stack was optimized to streamline the loading of Java bundles during the initial launch of the Notes 8.0.2 and 8.5 clients.
We were able to reduce redundancies and dependencies inherent in a highly integrated application. Additionally, we have re-ordered the startup sequence. This means that we load only the things necessary to get to your Inbox most quickly, loading other components either in the background, or when they are accessed by the application for the first time. The result is that the Notes 8.0.2 and 8.5 clients launch more than twice as fast as the Notes 8.0.1 client.
via IBM – Performance improvements from Notes 8.0.1 to 8.0.2 and 8.5.