You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every worker owns a connection to a storage. Currently WorkerCount value in BackgroundJobServerOptions is being calculated as a ProcessorCount * 5 value. In usual cases this value is ok as a default, but consider you have a 20-core server. In this case there will be 100 workers, and it is fine. However, since each worker use a connection, this value can produce errors:
SQL connection pool have 100 connections by default.
To make things more predictable, the default value should have a maximum at, for example, 40 to produce enough workers and leave some connections for other components.
The text was updated successfully, but these errors were encountered:
Hi @odinserj, seems like BackgroundJobServerOptions still allows only a maximum of 20 workers. Is it still required to be max 20, or can it be increased/overridden somehow?
Hi @odinserj, seems like BackgroundJobServerOptions still allows only a maximum of 20 workers. Is it still required to be max 20, or can it be increased/overridden somehow?
Every worker owns a connection to a storage. Currently
WorkerCount
value inBackgroundJobServerOptions
is being calculated as aProcessorCount * 5
value. In usual cases this value is ok as a default, but consider you have a 20-core server. In this case there will be 100 workers, and it is fine. However, since each worker use a connection, this value can produce errors:To make things more predictable, the default value should have a maximum at, for example, 40 to produce enough workers and leave some connections for other components.
The text was updated successfully, but these errors were encountered: