Page History
...
JVM 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.
...
- 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 there is plenty of free real memory available on the OS level, Servers in general just run faster when not memory constraint. (When 2Gb free real memory is left, just add the 2Gb to the JVM max memory. It will stays unused otherwise, the JVM will not take more memory then assigned ever.)
- When the expected client load will exceed the maximum: As a rule of thumb:
- Smart Client: assume a memory usage of about 600kb for each Smart Client. NOTE: When the Servoy HTTP Tunnel is used, assume 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.
...
Database Connection Pool Tuning
Databases have a max connection poolsize to prevent memory problems, but the default 10 can be too low when using many clients on 1 server.
As rule of thumb, if the active connection is > 70% of the max then set the max higher, its however not advised to have more then 30 connection max. (since databases them self have limits on how much they can handle, postgress for example default 40 max)
The idle connection parameter is just for efficient memory usage, when allow many idle more memory is occupied when idle, low idle means more connections have to be created (which is expensive time wise)
| Note |
|---|
When noticing performance problems also watch the "performance data" section. At all times the normal Servoy SQL should be below 0.5 seconds not including reporting or search queries. If this is not the case contact an database administrator for index creation. |
Servoy Application Server log
At all times try to keep the Server log free from javascript application errors/excpetions, all application exceptions point to possible problems inside the application!
...
. |
Servoy Application Server settings for Web Client Tuning
...
Details on setting up mod_deflate on an Apache HTTPD server can be found here: http://httpd.apache.org/docs/2.0/mod/mod_deflate.html
Servoy Application Server log
At all times try to keep the Server log free from javascript application errors/excpetions, all application exceptions point to possible problems inside the application!
Out of memory errors means the heap size is configured to small.
Nullpointer errors indicate Servoy codebase problems, incase these are noticed file a support case containing the log entry.
Network error are only listed as non critical (orange) which may point to (possible) networks (config) problems, when many errors are continuous listed these should definitely be investigated.
Overview
Content Tools
Activity