This article summarizes the settings used in publish process to control number of threads and batch size at publish.
Performance settings for threads
The number of parallel threads used when communicating with SQL server can be adjusted based on settings in server.config for Signifikant Manager or Signifikant Server.
<SqlServerDatabaseSettings>
<MaxParallelPublisherThread>5</MaxParallelPublisherThread>
<ChunkCount>5000</ChunkCount>
</SqlServerDatabaseSettings>
MaxParallelPublisherThread is used to control number of parallel requests are made to SQL Server during publish process. The number of threads may have to be adjusted based on type of processor used and how heavly load that should be put on SQL Server.
ChunkCount determines the size of each piece of information. E.g. when copying nodes in batch, what is the size of batch. Each chunk has an overhead cost, but more chunks are more easily put in separate threads. Too large chunks may cause memory problems. Typically use 1000 to 10000 as size.
Retries of file upload to web server
If publish finalize stage, where files are moved to web server, by some reason fails to respond to a request, e.g. by bad connectivity, Signifikant Manager/Server will retry the operation before aborting process.
<PublisherSettings>
<RemoteUploadTryCount>5</RemoteUploadTryCount>
</PublisherSettings>
RemoteUploadTryCount determines how may times a failed operation will be retried before aborting upload process.
Related articles