Page History

...

• Too little memory available: The Smart Client is a Java process and as such it needs to be explicitly told the maximum amount of memory it is allowed to use. For more information on memory management for Smart Clients see Smart Client memory management in the Memory Management chapter
• Connection issues: if the network connection is not stable, this could have a negative impact on teh the Smart Client performance. Enable the Java WebStart log to see if there are a lot of network related exceptionsIf for example a firewall or NAT router automatically starts closing connections because it can't handle many open connections, there will be a performance penalty due to the fact Servoy tries to use a connection that is already closed and then need to establish a new connection. By lowering the RMI Connection timeout the use of already closed connections can be prevented. See Network related settings for more information on network configurationRMI connection timeout
• Database connection pool exhaustion: When the solution that is run in the Smart Client required database access, it sends the request to the Servoy Application Server that in turn communicates with the database. It does so using a pool of connections. If all clients do more requests at the same time than the maximum allowed number of connections in the pool, the requests will take longer to execute, as they will be on hold untill a used connection is released back to the pool. For more information on Connection pooling, see Connection pooling in the Database Connections chapter 

...