...
Performance will be greatly improved if the following line is set in cipango.sh /etc/default/jetty
No Format |
---|
JAVA_OPTIONS=="-Xmx1700M -Xms1700M -XX:+UseParNewGC -XX:+UseConcMarkSweepGC" |
To allow Cipango to use more than 2 Gb of RAM, you should use a 64 bits OS and JVM.
See in Configuring and Running and stoppingCipango to see how to set this JVM property.
...
Info |
---|
These parameters are not set by default in order to allow to run Cipangp Cipango on computers with few memory. |
...
Log configuration
message tracing should be disabled: Ensure in cipango.xml, that the following XML is commented.
Code Block | ||||
---|---|---|---|---|
| ||||
<Set name="accessLog">
<New class="org.cipango.server.log.FileMessageLog">
...
</New>
</Set>
|
...
As written in sip servlet specification, for reasons of performance, it is recommended that applications explicitly invalidate SIP application session and SIP session objects as soon as possible.
TCP and UDP received buffer size
If there is some retransmissions and CPU is not at 100% usage, this could be the sign that buffer size is too small: some packets are destroyed by the OS before its can be handled by JVM.
More details on buffer sizing are available on http://www.29west.com/docs/THPM/udp-buffer-sizing.html
Detection
To detect packets lost due to small received buffer size, use the command:
OS | Command |
---|---|
Linux | |
Solaris | |
Windows | Impossible to detect |
AIX | |
FreeBSD | |
Setting buffer size
OS | Command |
---|---|
Linux | |
Solaris | |
FreeBSD, Darwin | |
AIX | |
Detect memory leaks
We recommend to use YourKit Java Profiler.
Tip |
---|
YourKit is kindly supporting open source projects with its full-featured Java Profiler. |