Page History

...

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 JVM 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

...

Checking whether or not a Servoy Application Server runs in client or server mode can be seen on the Servoy Admin page, under "Servoy Server Home" > "Servoy Server Status" > "JDK JVM Information": *

• Server mode: java.vm.name=Java HotSpot(TM) 64-Bit Server VM

...

• Client mode: java.vm.name=Java HotSpot(TM) Client VM

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.

...

• The actual used memory is >= 70% of the specified maximum. The actually used memory can be found on the main page of the Admin page, under System Information, like: Heap memory: allocated=549184K, used=371473K, max=699072K
• When the expected client load will exceed the maximum: As a rule of thumb:
  • Smart Client: assume a memory usage of about 300kb 600kb for each Smart Client. NOTE: When the Servoy HTTP Tunnel is used, assume 600kb 900kb per Client.
  • All other type of Clients (Web, Headless, Batch): the required memory for each client depends on the size and design of the solution, but should be in the order of magnitude of a couple of Mb per Client.

...