IBM® Sametime® administrators can make adjustments to the servers they maintain to provide optimal performance for users as they use instant messaging and web conferencing.
Complete the following tuning procedures to enhance performance.
Complete the following procedures to enhance performance.
Set verbose garbage collection logging in the IBM® Sametime® Connect Client.
If your IBM® Sametime® server is hosted on Linux™, increase the number of concurrent open files on the server to prevent performance problems.
By default, the Meeting Room Center searches the Meeting Room Center database for rooms without using an index. If the database becomes too big, your deployment might experience performance degradation during searches. You can enable full-text indexing on the room name and owner name fields for enhanced performance on large datasets.
Improve LDAP performance by configuring context pools using specific settings, disabling nested group search and configuring member and membership attributes.
You can manage advanced configuration settings for the maximum and minimum (MAX/LOW) number of LDAP requests that are pending per connection in the pending queue.
There are different types of bind operations supported by the LDAP protocol. The most common are anonymous and simple bind, also known as authenticated bind.
You can edit advanced configuration settings to increase the number of Connections per Sametime® module.
You can manage advanced configuration settings to make sure that there is consistent traffic over the LDAP connection.
You can manage advanced configuration settings to set how often the connection to the LDAP server should be dropped and re-established.
You can manage advanced configuration settings to define the LDAP maximum number of results per search query.
You can manage advanced configuration settings to define the minimum number of characters in the search string required to perform a search.
You can manage advanced configuration settings for controlling contact list size. By default, there is no limit to the number of contacts in the list.
You can have the Sametime® Polling service keep a client request alive for a certain number of second in cases where a temporary connection loss prevents an immediate response. The setting applies to clients who connect through HTTP and use the Sametime Polling service.
The Sametime® Community Server uses search optimization to speed up performance for user login and searches across an LDAP directory, allowing the system to handle a high load of searches. When the user authentication login or user search in the directory is an email address, the usual search filter is not used by the Sametime Community Server; instead only the mail attribute is searched. Using a Java™ customized search filter automatically disables the mail search optimization.
Improve IBM® Sametime® Meeting Server performance by setting custom properties.
Complete the following tuning procedures to enhance performance on an IBM® Sametime® Advanced Server.
This section contains procedures for tuning an IBM® WebSphere® SIP proxy server that is deployed in front of a cluster of IBM Sametime® servers.
Improve Sametime® Proxy Server performance by increasing JVM heap size, adjusting web container transport settings, as well as other setting other tuning parameters as explained in this section.