This documentation relates to last stable version of Cipango.
visit the last unstable documentation home.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

JVM Configuration

Cipango performance configuration is mainly function of JVM memory configuration.
The memory needed is function of number of concurrent calls, application, session duration.

Performance will be greatly improved if the following line is set in cipango.sh

JAVA_OPTIONS=="-Xmx1700M -Xms1700M -XX:+UseParNewGC -XX:+UseConcMarkSweepGC"

See in Running and stopping to see how to set this JVM property.

Adapt maximum heap size (-Xmx) and minimum heap size (-Xms) with memory available.

Ensure that in every case only RAM is used. (no swap used)

These parameters are not set by default in order to allow to run Cipangp on computers with few memory.

log configuration

message tracing should be disabled: Ensure in cipango.xml, that the following XML is commented.

<Set name="accessLog">
   <New class="org.cipango.log.FileMessageLog">
      ...
  </New>
</Set>

Servlet

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.

  • No labels