There is no special config that would generally make it work faster...
You have to find the 'bottleneck'. See what is the reason it takes long. A few ideas:
- is your server's hardware too crowded? (does it happen only when many clients are accessing the server at the same time)
- check the database query execution times in admin page (clear page, reproduce, see what happened query wise)
- if you can reproduce it using a developer and maybe accesing the developer-running solution, use the developer's 'Profile' view (Window -> Show view) to see what javascript executes and how long each method call takes when it reproduces. This might hint to possible slow methods in your code or in the framework. If you notice something in your code, try to optimize that; if you find something you think is too slow in frameworks, you should ask someone from frameworks.
- can you reproduce it only when using a non-local or non-lan client - so a client that has slower network throughput and higher latency?
- if you find no explanation in the above, or something points out to a Servoy API call/Servoy logic that you think takes too long it could be profiled at java level - and you would need to create a case for that.
- if you are using web-client, browser side developer tools can be used further to see what's going on (maybe too large parts of the page get updated when they shouldn't or something like this).
You could also end up concluding that it just takes a long time because there's loads of content in the page. In which case you might want to show less-at-a-time.
Like having 3 table-views showing lots of records with hundreds of columns, then some media, ...