Changes between Version 13 and Version 14 of ServerconfigWebConfigIni

Timestamp:

Jul 2, 2010, 12:24:55 PM (14 years ago)

Author:

trevorwekel

Comment:

--

ServerconfigWebConfigIni

@@ -91 +91 @@
 !MaxConnections determines the maximum number of web tier connections the server will accept.  For !MapGuide 2.1 and earlier on Windows, the total number of connections (administrative + client + site) must be no greater than 62 connections.  On the 63rd connection attempt, the server will become unresponsive.  For !MapGuide 2.2 on Windows and all versions of !MapGuide on Linux, the supported connection limit is greater than 500 connections.
 
-To fully utilize all cores on a !MapGuide server machine, there should be 1 administrative, 3 client, and 2 site connections per core.  Assigning additional connections may reduce request queue lengths and make better utilize server resources if longer delay features sources like WMS, WFS, and databases are used.  For local on-disk feature sources like SDF and SHP, the  1/3/2 per core listed above will typically be sufficient.
+To fully utilize all cores on a !MapGuide server machine, there should be 1 administrative, 3 client, and 2 site connections per core.  Assigning additional connections may reduce request queue lengths and better utilize server resources if longer delay features sources like WMS, WFS, and databases are used.  For local on-disk feature sources like SDF and SHP, the  1/3/2 per core listed above will typically be sufficient.
 === !QueueSize ===#ServerQueueSize
 The request queue size should be set to at leat !MaxConnections - !ThreadPoolSize.  Setting the queue size too low could lead to request loss under heavy load.
 === !ThreadPoolSize ===#ServerThreadPoolSize
-To fully utilize all cores on a !MapGuide server machine, there should be 1 administrative, 3 client, and 2 site threads available per core.  Increasing the thread pool size further may reduce request queue lengths and make better utilize server resources if longer delay features sources like WMS, WFS, and databases are used.  For local on-disk feature sources like SDF and SHP, the  1/3/2 per core listed above will typically be sufficient.
+To fully utilize all cores on a !MapGuide server machine, there should be 1 administrative, 3 client, and 2 site threads available per core.  Increasing the thread pool size further may reduce request queue lengths and better utilize server resources if longer delay features sources like WMS, WFS, and databases are used.  For local on-disk feature sources like SDF and SHP, the  1/3/2 per core listed above will typically be sufficient.
 
 == [!ClientConnectionProperties] Section ==#ServerClientConnection