I believe the most important factor in whether connection pooling will be useful is how complex your schema is. The more complex your schema, the longer it will take to open a new connection.
Remember the choice should not be between using a single static connection and a connection pool but should be between creating a connection every time you need one and using a pool. So concurrency does not change with a pool--you still have many connections. The only difference is you're reusing connections so you don't have to parse the schema so much. Also, SQLite's cache is done on a connection basis so reusing connections can give you some performance improvements in that data will already be cached from a previous call (assuming subsequent calls use similar data pages). The link I pointed to is Win32 only dll. However, Mono 1.2.4 uses the same source code as the link I pointed to (presumably with cross-os mods). Here's a post with more info: http://sqlite.phxsoftware.com/forums/thread/2624.aspx I'll post my connection pooling code as soon as I have time. Best regards, Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: Dinesh Ramdass [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 11, 2007 12:51 PM To: sqlite-users@sqlite.org Subject: Re: [sqlite] How to implement connection pooling thanks for the reply.... But i have some clarifications though... I downloaded System.Data.SQLite Dll from the website u mentioned but i was clearly stated that i was for Win32 systems.. ie for WIndows OS only... And i am using Linux. So is there a release for linux also? correct me if i am wrong... Also can u give me some sample code which implements connection pooling... And one more thing... From ur reply, i came to conclusion that Mono.data.SQLite does not provide pooling... we have to do it programmatically but having one static connection and managing threads... Also i have to convince my tech lead that connection pooling is not required in my scenario.. My scenario is I have max of 5-6 inserts/deletes/updates in one time... Max of some 10-20 selects at a time... Also any database activity is needed once in 2 hrs or so... Also i am managing write operation across threads..and also i am opening and closing connection immediately after use... SO do i need connection pooling really? Thanks and regards, Dinesh.R ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
