Performance tuning is an on-going activity and there are many factors that can influence the performance of a Lotus Notes Traveler server performance. These factors include host system resources, the number of devices, the network efficiency, the overall server load, the amount of data transferred to the devices, and the level of code being run. We explain how to review your server and configure the related parameters so that the server will run efficiently.
Lotus Notes Traveler high availability considerations
- When deploying Lotus Notes Traveler on VMware, to avoid having a single point of failure, place each Traveler server in the Traveler server pool on a separate VMware ESX server.
- For each Lotus Notes Traveler server, keep the number of devices under 2,500.
- Note the Maximum number of 2500 devices is per server after a failover has occurred.
- Have 4 processor cores and 16 GB memory for each Traveler server in the pool.
- Use 64-bit operating system for Lotus Notes Traveler and Lotus Domino (where supported)
- Adjust the Java Max Memory as more devices are added
Latest software version
The Lotus Notes Traveler maintenance release contains the latest fix for the code stream. It is always a good idea to stay on the latest release of the Lotus Notes Traveler software. For the
latest version of the 18.104.22.168+ software, see the Recommended Maintenance - Lotus Notes Traveler
. The Lotus Note Traveler team attempts to stay on top of all the new device operating systems and levels that are released. Because of this, when a new device code level is released, look to the Recommended Maintenance - Lotus Notes Traveler
for the latest Lotus Notes Traveler code to address the new device code levels.
Data filter settings
The data filter settings influences the amount of data that is synchronized between the devices and the Lotus Notes Traveler server. By setting these parameters, you can avoid a user tying up the resources when trying to synchronize large amounts of data.
These parameters are defined in the default device settings, and can be overwritten for a certain user group by a dynamic security policy that can be implemented on the Domino server. The Lotus Notes Traveler Server first uses a dynamic security policy if this is in place for the particular user over the default device settings on the Lotus Notes Traveler server. If there is no dynamic security policy in place for the user in question, the default device settings is used.
To adjust the parameter value, select the Preferences
tab and then the Filter Settings
tab. The default value is Unlimited, meaning that no filter is applied by the server. To set a filter limit, enter a number in days for one of the following settings. While mobile device users can set their filter limit lower than the defined maximum, anything higher will not be honored by the server.
- Email filter limit
New mail older than the Email filter limit will not be synchronized with the device.
- Past events filter limit
Calendar events older than the past events filter limit will not be synchronized with the device. Note that recurring events that have an instance within the filter window will be synchronized, even if they have instances that start earlier that the past events filter limit.
- Future events filter limit
Calendar events in the future that occur beyond the future events filter limit will not be synchronized with the device. Note that recurring events that have an instance within the filter window will be synchronized, even if they have instances that occur beyond the future events filter limit.
- Journal filter limit
Journal entries modified earlier than the limit will not be synchronized to mobile devices that support Journal sync. This is currently only supported in Windows Mobile devices.
Log level options
Log information is essential for monitoring server performance and troubleshooting. The more information is collected, the more disk space is required and the more overhead is seen on the Lotus Notes Traveler server. The base logging level for the Lotus Notes Traveler INFO. To set the entire server to the INFO level for logging, run the tell traveler log level info
command. Modify the log level only if there is a reason for increased logging.
It is not
reccomended to set the logging level to FINEST for the server. Please only use FINEST logging for a single user. Since this Wiki was created we have released Upgrade Pack 2, and some additional information for log collection. Please reference this link
for this more current documentation. The information in Upgrade Pack 2 Gathering log file support section contents can be applied for Upgrade Pack 1 application.
This section covers the hardware specifications and configuration parameters that can influence the enterprise database performance.
Consider the following software and hardware specifications for the Lotus Notes Traveler database server:
● For large enterprise deployment, Use physical servers for the database servers
● Place the data and transaction log volumes on separate storage hardware RAID LUNs.
● Data and Transaction Log volumes must be able to support the sustained I/O (Input/Output) operations per second (IOPs) required.
● For a database server supporting up to 10,000 devices in a Lotus Notes Traveler Server pool:
o Use 8 processor cores, 32 GB memory, and 1,000 sustained IOPs.
o Use a dedicated (not shared with other applications) hardware RAID 5 (or better) LUN with 8 disks (8,000 to 10,000 devices) for the Lotus Notes Traveler database.
o Use a dedicated (not shared with other applications) hardware RAID 1 (or better) with 4 disks for transaction log.
o The LUNs are dedicated, the storage system can be shared.
● For up to 8,000 devices, 6 disks are needed for the LUN that the Lotus Notes Traveler database uses.
● Database servers should use DB2 HADR or Microsoft SQL for full HA (requires 2 database servers).
● DB2 for Linux, UNIX, and Windows 9.7 FP5 or later and Microsoft SQL Server Enterprise 2008 R2 SP1 or later are required.
It is important to note that the storage system used for the database servers must be able to support the SUSTAINED IOPs required. For example, if a high end storage such as the IBM XIV® Storage System is used, then configure the storage LUNs for the required sustained IOPS,
The Lotus Notes Traveler DB2 database buffer pool can be set to 1- 2 GB based on available physical memory on the server and the user load. As an example, for a Lotus Notes Traveler pool supporting 8,000 devices, use a buffer pool up to 2 GB on a DB2 server running with 8-16 GB memory.
Consider the following DB2 database configuration parameters for a Lotus Notes Traveler deployment:
- LOGBUFSZ: Log buffer size, a good starting point to set this is 8192.
- LOGFILSIZ: Log file size, A good starting point to set this is 8192.
- MINCOMMIT: Number of commits to group, a good starting point to set this is 1.
- LOGPRIMARY: Number of primary log files, a good starting point to set this is 120.
- LOGSECOND: Number of secondary log files, a good starting point to set this is 10.
Ideally, the Lotus Notes Traveler servers and the mail servers will all be located at the same location. If the mail servers are located in a different location the latency may create a bottleneck on the server.
Go to the Internet Protocols, Domino Web Engine
Review the Memory Caches
The Maximum cached users
field is used to store a users name, password, and a list of groups that the user belongs to. A user is added to this cache after they successfully authenticate with the Lotus Notes Traveler server. The default setting for this field is 64. If the number of current authenticated users logged in exceeds this value, some performance improvements may be gained by increasing the number of the Maximum cached users. To review the current values, look at the statistics from a recent NSD file. As a general guideline, when adjusting any of the "Domino.Cache.*.Count" statistics, they should be slightly less than their "Domino.Cache.*.MaxSize" counterpart. In this case, the "Domino.Cache.User Cache.Count" should be slightly less than the "Domino.Cache.User Cache.MaxSize". If the value listed in the Domino.Cache.User Cache.Count is larger than the Domino.Cache.User Cache.MaxSize, then try slowly incrementing the maximum value for the "Maximum cached users", as shown in the Memory Cache section screen capture above, until the Count no longer reaches the Maximum. Given the resources this value should be roughly 3 times the number of users.
Go to the Transactional Logging
Disable Transactional Logging. The Lotus Notes Traveler server is not a typical server, as there is very little writing to Domino databases. With the small number of writes necessary, it is not necessary to enable Transactional Logging.