Re: [MonetDB-users] best practices with connection pool
Hi,All I found this subject in the archives, and I am having the same problem. ----------------------------------------------------------------------
What is currently the best practice of connecting to MonetDB5/SQL? Is there much overhead in the connection phase (thus: cache the connection) or can a developer just reconnect each time the database connection is required without much overhead?
The target platform is extremely demanding in requests and memory, so I would like to design it good from the start.
Then go for connection pooling. Logging in requires a handshake, which is expensive on large scale. Beware that using >1 connection at the same time to an SQL server is a challenge that is only minimally tested. My practical experiences with that boils down to signal 11.
Would you let me know more detail? Your meaning of "Beware that using >1 connection at the same time..." is which case? Case 1. : 2 or more process try to connect at the same. Case 2. : 1 process is connecting, and other process try to connect. I appreciate your kindly support. gashi
On 29-09-2008 09:56:48 +0900, gashi gashi wrote:
is expensive on large scale. Beware that using >1 connection at the same time to an SQL server is a challenge that is only minimally tested. My practical experiences with that boils down to signal 11.
Would you let me know more detail? Your meaning of "Beware that using >1 connection at the same time..." is which case?
Case 1. : 2 or more process try to connect at the same. Case 2. : 1 process is connecting, and other process try to connect.
Both. In particular when both processes are executing queries. Theoretically this work, of course.
Hi,Fabian
Thanks.
In addition, there is a question.
Should "select" process be one connection?
Regards,
gashi
2008/9/30 Fabian Groffen
On 29-09-2008 09:56:48 +0900, gashi gashi wrote:
is expensive on large scale. Beware that using >1 connection at the same time to an SQL server is a challenge that is only minimally tested. My practical experiences with that boils down to signal 11.
Would you let me know more detail? Your meaning of "Beware that using >1 connection at the same time..." is which case?
Case 1. : 2 or more process try to connect at the same. Case 2. : 1 process is connecting, and other process try to connect.
Both. In particular when both processes are executing queries. Theoretically this work, of course.
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ MonetDB-users mailing list MonetDB-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/monetdb-users
participants (2)
-
Fabian Groffen -
gashi gashi