Difference between revisions of "Tuning Report Threads"
From AgileApps Support Wiki
imported>Aeric |
imported>Aeric |
||
| Line 1: | Line 1: | ||
=== Tuning Report Threads === | <includeonly>=== Tuning Report Threads ===</includeonly> | ||
The number of report threads can be configured in the <tt>[[Platform Installation Guide/networking.properties | networking.properties]]</tt> file: | The number of report threads can be configured in the <tt>[[Platform Installation Guide/networking.properties | networking.properties]]</tt> file: | ||
Revision as of 21:33, 2 October 2013
The number of report threads can be configured in the networking.properties file:
- report_threads=2
- Assigns number of threads to be used by the report server.
Generally, two threads devoted to reporting is about right. If reports aren't arriving on time, consider incrementally expanding the number of threads to see if performance improves (while keeping an overall eye on system resources, to ensure that increasing the number of threads does't incur other bottlenecks.
For maximum reporting efficiency (if needed), setup a dedicated backend server for reporting. Learn More: Managing Backend Services