In this blog, I am going to list the best tuning settings for ATG Search engine.
The AESoapConfig.xml, AESoapWaspConfig.xml and AEConfig.xml are the xmls referred below and you can find it @ <ATG_DIR>\<Searchx.x>\SearchEngine\<operating_system>\bin\ folder.
(1) Make sure that the AESoapConfig.xml's rwTimeout is less than or equal to routing's readTimeoutMs. You could find the routing's readTimeoutMs @ atg\search\routing\SearchEngineService component.
rwTimeout is the length of time in seconds to wait before a read or write operation times out on an active connection. The number can be decreased to improve performance. However, a value that is too low could cause slow connections to be prematurely closed.
(2) Adjust the number of engine threads to match the number of CPUs available to the engine. Note that the minimal value for maxThreads and maxSpareThreads is 2, which applies to running with 1 CPU. However, it is recommended to run with more than one CPU.
a) Set MaxThreads in AEConfig.xml to number of CPU's
b) Set maxSpareThreads in AESoapWaspConfig.xml to number of CPU's
maxThreads is the number of requests you can process simultaneously, and this generally should be the number of CPU's available to the engine. If this is higher than the CPUs, the engine will bog down, with slower response times.
maxSpareThreads is the number of worker threads to process requests simultaneously, generally this should be the same as MaxThreads.
(3) Disable the the keep-alive/connection reuse setting
a) Set reuseCount=0
reuseCount is the number of requests that may be accepted using the same connection. The number can be increased to reduce the frequency of opening new connections and improve performance. However, a value that is too high could prevent new connections from being accepted. A value of 0 disables connection reuse. This applies to HTTP 1.1 only.
The AESoapConfig.xml, AESoapWaspConfig.xml and AEConfig.xml are the xmls referred below and you can find it @ <ATG_DIR>\<Searchx.x>\SearchEngine\<operating_system>\bin\ folder.
(1) Make sure that the AESoapConfig.xml's rwTimeout is less than or equal to routing's readTimeoutMs. You could find the routing's readTimeoutMs @ atg\search\routing\SearchEngineService component.
rwTimeout is the length of time in seconds to wait before a read or write operation times out on an active connection. The number can be decreased to improve performance. However, a value that is too low could cause slow connections to be prematurely closed.
(2) Adjust the number of engine threads to match the number of CPUs available to the engine. Note that the minimal value for maxThreads and maxSpareThreads is 2, which applies to running with 1 CPU. However, it is recommended to run with more than one CPU.
a) Set MaxThreads in AEConfig.xml to number of CPU's
b) Set maxSpareThreads in AESoapWaspConfig.xml to number of CPU's
maxThreads is the number of requests you can process simultaneously, and this generally should be the number of CPU's available to the engine. If this is higher than the CPUs, the engine will bog down, with slower response times.
maxSpareThreads is the number of worker threads to process requests simultaneously, generally this should be the same as MaxThreads.
(3) Disable the the keep-alive/connection reuse setting
a) Set reuseCount=0
reuseCount is the number of requests that may be accepted using the same connection. The number can be increased to reduce the frequency of opening new connections and improve performance. However, a value that is too high could prevent new connections from being accepted. A value of 0 disables connection reuse. This applies to HTTP 1.1 only.
Comments
Post a Comment