Timeline for PHP: Injecting the same database connection into multiple objects
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2015 at 18:21 | comment | added | concat | I'm running into mysqli::mysqli(): (08004/1040): Too many connections when creating more than max_connections number of objects, even when using persistent connections. I am unsure as to what exactly "Every PHP process is using its own mysqli connection pool." entails, but it doesn't seem to be what we expect. | |
| Jun 21, 2015 at 19:53 | vote | accept | concat | ||
| Jun 21, 2015 at 17:33 | comment | added | concat | True! "Every PHP process is using its own mysqli connection pool." | |
| Jun 21, 2015 at 17:28 | comment | added | Arseni Mourzenko | @concat: with database connections pooling, you don't have to reuse a connection. Open it when you need it; do your job; close the connection as soon as you don't need it any longer. Reading the manual, it seems that mysqli in PHP supports pooling, so I wouldn't worry about that. You may start to worry only if and when the profiling will tell you that this part becomes an actual bottleneck. | |
| Jun 21, 2015 at 17:22 | comment | added | concat | Fair point. However, wouldn't I still be faced with spawning a lot of DB connections? It's this, not the parsing of the configuration file, that I'm concerned will be prohibitive. Perhaps I am unclear on the exact responsibilities of the configuration parsers. | |
| Jun 21, 2015 at 17:15 | history | edited | Arseni Mourzenko | CC BY-SA 3.0 | added 649 characters in body |
| Jun 21, 2015 at 17:07 | history | answered | Arseni Mourzenko | CC BY-SA 3.0 |