Child pages
  • Tuning the Server

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Servoy Application Server Tuning

Java version

Servoy supports both Java 5 and Java 6 (for the server, the clients and developer). Java 6 has numerous performance improvements, so it is preferred over Java 5.

When the hardware of the Servoy is 64bit, make sure to also run a 64 bit Java Virtual Machine. When in doubt which version is used, check the Servoy Admin page, under "Servoy Server Home" > "Servoy Server Status" > "JDK Information":

* 64 bit: java.vm.name=Java HotSpot(TM) 64-Bit Server VM
* 32 bit: java.vm.name=Java HotSpot(TM) Client VM

Java Virtual Machine Server mode

...

If the JVM supports servermode, it will automatically detect if the machine it is running on is a "capable" machine and automatically run in server or client mode depending. The definition of "capable" may differ from Java version to Java version. For Java 5/6 this means a 2CPU, 2Gb memory machine.

...

It is possible to enforce the Servoy Application Server to run in server mode (assuming the JVM is capable to operate in server mode), an extra startup argument can be added to the startup of the Servoy Application Server.

In servoy_server.sh/bat:

Code Block

java -server -Djava.awt.headless=true .....

When using the Service wrapper:

Code Block
# Java Additional Parameters
wrapper.java.additional.1=-Djava.awt.headless=true
wrapper.java.additional.2=-Duser.dir="C:\Users\pbakker\Desktop\tmp servoy\application_server"
wrapper.java.additional.3=-XX:MaxPermSize=128m
wrapper.java.additional.4=-server
Note
JVM servermode on windows 32-bit
JVM servermode on windows 32-bit

On Windows 32 bit environments , the Java Runtime Environment does not include support for server mode. In order to take advantage of server mode optimizations on 32 bit windows systems, it is required to install Java Development Kit (JDK)

...

Note
Tomcat Compression configuration as of Servoy 6.0
Tomcat Compression configuration as of Servoy 6.0

As of Servoy 6.0, the Tomcat compression configuration will be enabled by default

It is also possible to handle the compression outside of the Servoy Application Server, for example in an Apache HTTPD Server placed between the Servoy Application Server and the outside world. The advantage of this is that Tomcat's compression options are limited, so an external HTTP server offers more options.

When it comes to Apache HTTPD server, there are two options:

...