17 October 2007

MaxConcurrentConfigRequests value changed after Notification Server 6.0 SP3 upgrade

After upgrading to Notification Server 6.0 SP3, the MaxConcurrentConfigRequests settings were reduced from 50 to 10 in the CoreSettings.Config file.

This is by design. The default value of MaxConcurrentConfigRequests was lowered from 50 to 10 in Notification Server 6.0 SP3, and that modification is made during the SP3 upgrade.

________________________________

Resolution


After significant evaluation of this setting both internally at Altiris and at customer sites, it was concluded that the default setting of 50 for the MaxConcurrentConfigRequests value was too high for normal operations of Notification Server and could actually be detrimental to performance in particular circumstances.

Notification Server 6.0 SP3 also added MaxConcurrentPackageInfoRequests as a separate value for limiting GetPackageInfo requests, also with a default value of 10. Prior to SP3, GetClientPolicy requests and GetPackageInfo requests were both limited under the same MaxConcurrentConfigRequests setting which could cause contention for connections between these two separate operations when the MaxConcurrentConfigRequests value was lowered.

These default values for MaxConcurrentConfigRequests and MaxConcurrentPackageInfoRequest should only be increased when specific monitoring shows doing so will provide improved performance. Setting these values too high can be detrimental to performance and lead to database deadlocks and database connection failures.

No comments: