Improving Job execution time
remoteDataRetriever.threadPool.size parameter can be used to improve job execution time when many Jobs are running simultaneously.
This parameter produces longer running Jobs, which is meant to address a side effect of the current log retrieving mechanism: each execution implies a new thread, which in turn increases the number of tasks and induces Job execution delays.
Go to the configuration table of the database and edit remoteDataRetriever.threadPool.size value (number of threads in the pool). By default, the value is set to 30 threads.
Information noteNote: If you need to go back to the old log retrieving mechanism, go to the
configuration.properties file and set
jobserver.log.retriever.deprecated to
true. In this case,
remoteDataRetriever.threadPool.size is ignored. With the
old log retrieving mechanism, the number of tasks is reduced but the memory
consumption is increased.
Did this page help you?
If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!