Timeline for Creating database connections - Do it once or for each query?
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2018 at 18:25 | comment | added | Henka Programmer | The MySQL Connector/Net supports connection pooling for better performance and scalability with database-intensive applications. This is enabled by default. | |
| S Oct 3, 2016 at 18:12 | history | suggested | 8128 | CC BY-SA 3.0 |
update to latest version of Microsoft article
|
| Oct 3, 2016 at 8:39 | review | Suggested edits | |||
| S Oct 3, 2016 at 18:12 | |||||
| Nov 22, 2015 at 16:12 | comment | added | pdr | @AlexVPerl: I'd need to profile and see evidence that a) there is an actual saving in not returning the connection to the pool and b) that cost isn't a result of hitting the max connection pool (cause, if it did, then any saving would mean a cost elsewhere -- potentially even timeouts waiting for a connection). I'd also need to know that there weren't any other costs, like problems caused by connections dropping between calls. I'd also need to be worried about millisecond-level efficiency savings. An unlikely use-case, but never say never. | |
| Nov 22, 2015 at 0:48 | comment | added | AlexVPerl | What about the cost of returning the connection to the pool itself. If you do it frequently enough that could outweigh the benefits. So in some use cases if queries are executed in a loop let say it could be faster to re-use 1 connection rather than returning and re-requesting it again and again from the connection pool. | |
| Oct 2, 2012 at 17:33 | comment | added | smdrager | It should known that opening, running a query, and disposing a connection, even in a loop, is equally as fast, and sometimes FASTER than opening it once and looping the query. Always just dispose. It's more secure, and FAST. Do not worry about the overhead of the getting a connection from the pool--it is so trivial. | |
| Mar 29, 2012 at 18:50 | comment | added | pdr | @briddums: Depends on the provider assembly. I am certain that both Microsoft's Oracle implementation and Oracle's own both support connection pooling, because I've used them. I've heard that there's a MySql one that does, and I'd expect the providers in Spring.NET to support pooling, but you're better off searching or asking the provider directly than asking me. | |
| Mar 29, 2012 at 18:45 | comment | added | user43249 | @briddums - I think that depends on the connector. .Net, for example, doesn't provide a MySql connector. It's written and maintained by MySql. And whilst it works, in my experience the earlier implementation were far from bug free. | |
| Mar 29, 2012 at 18:32 | comment | added | briddums | The webpage you linked to is specific to SQL Server. Does .NET also provide automatic pooling when connecting to other databases eg - Oracle, Sqlite, MySql? | |
| Mar 29, 2012 at 11:54 | history | edited | pdr | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Mar 29, 2012 at 10:00 | vote | accept | webnoob | ||
| Mar 29, 2012 at 9:53 | history | answered | pdr | CC BY-SA 3.0 |