Lotus Traveler: Tunning English - Revision history

Ebasso: Página substituída por 'Page moved to Lotus Traveler: Tuning English'

2013-10-31T11:09:02Z

Página substituída por 'Page moved to Lotus Traveler: Tuning English'

Ebasso at 18:31, 29 September 2012

2012-09-29T18:31:30Z

← Older revision		Revision as of 18:31, 29 September 2012
Line 10:		Line 10:
	* '''HTTP threads''' - Used by the HTTP task, one per HTTP connection.		* '''HTTP threads''' - Used by the HTTP task, one per HTTP connection.


			== '''GENERAL:''' Optimizing Name lookup ==

			A good way to optimize Name lookup, is to configure the minimum number of characters in the search string required to perform a search.

			'''NTS_LOOKUP_MIN_LENGTH=3'''


			== Traveler Availability Index ==

			Availability Index (AI) used by Traveler servers in the pool to balance load.?

			The AI range can be from 100 to -200
			* 100 to 0 Normal processing range (base AI 100)
			* 0 to -100 Traveler server is in constrained state (base AI 0)

			** Constrained state is when the server recognizes it is overloaded and starts send 503 server
			busy responses in attempt to recover.

			* 00 to -200 Traveler server is unavailable (base AI -100)
			** Administrator has marked server as unavailable using tell command.
			? The AI is computed by subtracting the larger of the memory usage and
			CPU usage from the Base AI.
			Native
			memory is the percentage of Native memory use vs physical memory
			Average
			CPU percentage over last 15 minutes.

	=== System stat results ===		=== System stat results ===

Ebasso at 17:20, 25 September 2012

2012-09-25T17:20:04Z

← Older revision		Revision as of 17:20, 25 September 2012
Line 9:		Line 9:
	* '''Worker threads''' - Used internally in the device synchronization process.		* '''Worker threads''' - Used internally in the device synchronization process.
	* '''HTTP threads''' - Used by the HTTP task, one per HTTP connection.		* '''HTTP threads''' - Used by the HTTP task, one per HTTP connection.


			=== System stat results ===

			[http://www-10.lotus.com/ldd/dominowiki.nsf/dx/System_stat_results_A853UP1 System stat results]

	=== Default Values ===		=== Default Values ===

Ebasso: /* How to determine the current number of active HTTP threads */

2012-01-18T12:22:47Z

How to determine the current number of active HTTP threads

← Older revision		Revision as of 12:22, 18 January 2012
Line 54:		Line 54:


	== How to determine the current number of active HTTP threads ==		=== How to determine the current number of active HTTP threads ===

Ebasso: /* Example */

2012-01-18T12:12:01Z

Example

← Older revision		Revision as of 12:12, 18 January 2012
Line 44:		Line 44:


	=== ~~Example~~ ===		=== How to determine the current number of active devices ===

	To find out if you need to change this parameter, run the following command		Checkout for '''Push.Devices.Total''' statistics. To find out if you need to change this parameter, run the following command

	> tell traveler stat show		> tell traveler stat show
	...		...
	Push.Devices.Total = 225		Push.Devices.Total = 225
	...		...


			== How to determine the current number of active HTTP threads ==


			The current number of active HTTP threads allocated by the Domino web server at startup can be found in the Server document on the Internet Protocols -> HTTP tab in the Number active threads field.

	== Guidelines ==		== Guidelines ==

Ebasso: /* Default Values */

2012-01-18T12:09:21Z

Default Values

← Older revision		Revision as of 12:09, 18 January 2012
Line 44:		Line 44:


			=== Example ===

			To find out if you need to change this parameter, run the following command

			> tell traveler stat show
			...
			Push.Devices.Total = 225
			...

			== Guidelines ==
	The following are general guidelines for the relationships between the number of threads in each of the thread pools.		The following are general guidelines for the relationships between the number of threads in each of the thread pools.

Line 49:		Line 59:
	* Worker threads should be double the number of device sync threads.		* Worker threads should be double the number of device sync threads.
	* HTTP threads should be 1.2 times either the number of device sync threads or the number of ActiveSync devices, whichever is larger.		* HTTP threads should be 1.2 times either the number of device sync threads or the number of ActiveSync devices, whichever is larger.


	=== Statistics ===		=== Statistics ===

Ebasso: /* Example */

2012-01-18T12:03:20Z

Example

← Older revision		Revision as of 12:03, 18 January 2012
Line 175:		Line 175:

	The optimal value for the'''Hitrate''' is near 100%, and'''DisplaceRate''' is 0%. Increasing the value of the field'''Maximum cached designs''' improves response-time.		The optimal value for the'''Hitrate''' is near 100%, and'''DisplaceRate''' is 0%. Increasing the value of the field'''Maximum cached designs''' improves response-time.


			== Deciding which server performs the lookup ==

			By default, the lookup is performed against the user's mail server. This is done to reduce the configuration needed on the Traveler server and to provide more consistent results with a Notes client.

			You can change this behavior to perform the lookup operation against the Traveler server. To do this, set the following parameter in the notes.ini file:

			* NTS_TRAVELER_AS_LOOKUP_SERVER=True

Ebasso at 11:43, 18 January 2012

2012-01-18T11:43:22Z

← Older revision		Revision as of 11:43, 18 January 2012
Line 78:		Line 78:
	'''Reference'''		'''Reference'''
	\|		\|
	*		* [http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.help.lnt851.doc%2FTuning_performance_of_the_server.html Lotus Traveler Tuning performance of the server]
	\|}		\|}

Line 112:		Line 112:
	'''Reference'''		'''Reference'''
	\|		\|
	*		* [http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.help.lnt851.doc%2FTuning_performance_of_the_server.html Lotus Traveler Tuning performance of the server]
	\|}		\|}


	~~=== References ===~~

	~~[http://publib.boulder.ibm.com/infocenter/domhelp/v8r0/index.jsp?topic=%2Fcom.ibm.help.lnt851.doc%2FTuning_performance_of_the_server.html Lotus Traveler Tuning performance of the server]~~

	== Cache User Info - HTTP Maximum Cached Users - 64 bits only ==		== Cache User Info - HTTP Maximum Cached Users - 64 bits only ==

Ebasso at 11:40, 18 January 2012

2012-01-18T11:40:50Z

← Older revision		Revision as of 11:40, 18 January 2012
Line 53:		Line 53:
	=== Statistics ===		=== Statistics ===

	The first set of statistics is the device synchronization GetThreadDelayTime histogram, where you can see if there is a long delay before a device synchronization thread is allocated. This is an example of a device synchronization thread histogram:		{\| border="1"
			\|
			'''Statistics'''
			\|
			The first set of statistics is the device synchronization '''GetThreadDelayTime''' histogram, where you can see if there is a long delay before a device synchronization thread is allocated. This is an example of a device synchronization thread histogram:

			* ThreadPool.GetThreadDelayTime.DS.00-02
			* ThreadPool.GetThreadDelayTime.DS.02-05
			* ThreadPool.GetThreadDelayTime.DS.05-10
			* ThreadPool.GetThreadDelayTime.DS.10-Inf
			\|-
			\|
			'''Interpretation'''
			\|
	* ThreadPool.GetThreadDelayTime.DS.00-02 = 571071		* ThreadPool.GetThreadDelayTime.DS.00-02 = 571071
	* ThreadPool.GetThreadDelayTime.DS.02-05 = 45		* ThreadPool.GetThreadDelayTime.DS.02-05 = 45
Line 62:		Line 74:
	In this example the first line indicates that the majority of the device synchronization starts in the 0 to 2 second range. This implies that the current device thread count is sufficient for the load.		In this example the first line indicates that the majority of the device synchronization starts in the 0 to 2 second range. This implies that the current device thread count is sufficient for the load.

	The second set of statistics is the number of device synchronizations that have finished with various return codes (DeviceSync.Count.xxx). The return codes are:		\|-
			\|
			'''Reference'''
			\|
			*
			\|}



			{\| border="1"
			\|
			'''Statistics'''
			\|
			The second set of statistics is the number of device synchronizations that have finished with various return codes ('''DeviceSync.Count.xxx'''). The return codes are:

	* 200 - Successful		* 200 - Successful
Line 70:		Line 95:
	* 503 - Server Busy		* 503 - Server Busy

	DeviceSync.Count.503 shows the number of synchronizations that were not allowed to start and were ultimately aborted because a device synchronization thread could not be allocated to run the synchronization. This value should be much smaller than the DeviceSync.Count.200 value, which shows the number of synchronizations that have finished with a return code of 200 (Successful). If the DeviceSync.Count.503 value is too high, you should increase the number of device synchronization threads, which should reduce the occurrence of synchronizations that result in a server busy response.		\|-
			\|
	The following is an example of the DeviceSync.Count stats. In this case, the ratio of 503 results (4) to 200 results (43427) is very small, which indicates there is no need for additional device synchronization threads.		'''Interpretation'''
			\|
	* DeviceSync.Count.200 = 43427		* DeviceSync.Count.200 = 43427
	* DeviceSync.Count.408 = 199		* DeviceSync.Count.408 = 199
Line 79:		Line 104:
	* DeviceSync.Count.500 = 5		* DeviceSync.Count.500 = 5
	* DeviceSync.Count.503 = 4		* DeviceSync.Count.503 = 4

			DeviceSync.Count.503 shows the number of synchronizations that were not allowed to start and were ultimately aborted because a device synchronization thread could not be allocated to run the synchronization. This value should be much smaller than the DeviceSync.Count.200 value, which shows the number of synchronizations that have finished with a return code of 200 (Successful). If the DeviceSync.Count.503 value is too high, you should increase the number of device synchronization threads, which should reduce the occurrence of synchronizations that result in a server busy response.

			The following is an example of the DeviceSync.Count stats. In this case, the ratio of 503 results (4) to 200 results (43427) is very small, which indicates there is no need for additional device synchronization threads.
			\|-
			\|
			'''Reference'''
			\|
			*
			\|}

Ebasso: /* LOTUS TRAVELER THREAD POOLS */

2012-01-18T11:30:48Z

LOTUS TRAVELER THREAD POOLS

← Older revision		Revision as of 11:30, 18 January 2012
Line 1:		Line 1:
	== ~~LOTUS TRAVELER THREAD POOLS~~ ==		== Lotus Traveler Thread Pools ==

	=== Description ===		=== Description ===