Page History
...
Especially for SQL statements that are fired often and take up significant time it should be checked if it's possible to optimize the database, for example by creating the relevant indexes.
Foundset loading Tuning
Servoy loads a foundset by first retrieving the PKs from the database. This retrieval is done in chunks: when the foundset is initialized, the first chunk is retrieved, consequtive chunks are retrieved when needed.
The actual record data is also retrieved from the database in chunks.
The size if the different chunks are controlled by 3 properties that can be set in the servoy.properties:
Setting | Default Value | Description |
---|---|---|
servoy.foundset.pkChunkSize | 200 | Chunk size for foundset PK retrieval |
servoy.foundset.chunkSize | 30 | Chunk size for record data retrieval |
servoy.foundset.initialRelatedChunkSize | 2 * servoy.foundset.chunkSize | Chunk size for related record retrieval |
The values can be modified in an attempt to increase performance. The optimal values differ per application, thus no guidelines are available for alternative values. Tuning needs to be done by altering the values and monitoring the performance afterwards. The defaults are set based on averages.
Web Client Tuning
Content compression
...
Save the edits and restart the Servoy Application Server to let the configuration changes take effect.
Tuning of foundset loading
When Servoy loads a foundset, first the PKs are retrieved from the database.
This happens in chunks, when the foundset is loaded the first chunk is retrieved, next chunks are retrieved when needed.
When record data is retrieved from the database, this is also done in chunks.
There are 3 parameters that can be set in the servoy.properties file to control the size of these chunks:
...
.
Servoy Application Server log
...