Child pages
  • Database Connections
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Servoy relies on SQL databases for data storage. Servoy is database agnostic and can connect to any database that supports JDBC.

Connections to databases are configured on the Servoy Application Server and the Servoy Application Server will automatically create a pool of connections.

Clients never directly connect to a database, but instead connect to the Servoy Application Server, which handles the  

Connection Pooling

JDBC drivers

connection pooling works like this
at the moment a client (smart or web) does a query, it takes one from the pool if there is 1 idle (if not it will create one)
then if it is done it puts it back into the pool and it keeps idle connections until the max idle count 

Besides that you also have a max number of connections that are in use.. If that is reached then the next one cant get a connection until another releases one (gives it back as idle)

I think idle of 10 connections is fine for most useage, but do set the max number of connections a bit higher to handle peak connections
What exactly the right thing is is a bit hard to say maybe if you say that you can have max 100 users at the same time
you should have 50 max number of connections and 20 idle...
(so max is users/2 and idle could be users/5)

But this is also a bit depending on your solution, if you use long transactions for example then the max number should be users/1 ....

  • No labels