| Tomcat option adjustments that can improve Audium Call Services performance |
| Categories: Audium Call Services 3.6 |
| Article ID: | 312 |
| Last updated: | March 15, 2007 |
| User Opinions |
|
No users have voted.
|
|
Thank you for rating this answer.
|
SUMMARY
This article explains several Tomcat options that can be adjusted to improve the performance of Audium Call Services.
SYMPTOMS
Audium Call Services is working normally, but administrator would like to increase its performance (e.g. ability to handle higher load).
RESOLUTION
The following three Tomcat options can be adjusted to improve Audium Call Services performance:
- Set minProcessors to 100 and maxProcessors to 150. They can be increased if desired, but should not exceed the range of 200-400.
- Set acceptCount to a value of 1000.
- Your voice browser should be configured to use persistent connections. In HTTP 1.1, all connections are considered persistent and in HTTP 1.0, the keep-alive header is expected to appear in all requests made by the browser. While this is not a Tomcat option, it directly affects the performance of Tomcat when interacting with your voice browser.
We highly recommend that you refer to your system administrators to discuss these changes before implementing them, and also that you run tests to see how they affect your server's performance before using them in production. That said, we have found these adjustments to be helpful on many occassions.
|
| Visitor Comments |
|
No visitor comments posted. Post a comment
|
| Attachments |
|
No attachments were found.
|