You would ONLY use this for queries, never inserts/updates/deletes, UNLESS you had a multi-master situation where updates to any database serverautomatically replicate to the other servers (I don’t know whether that’s possible with MySQL).

Using this class, you get a connection to a MySQL server like this:
$con = MySQLConnectionFactory::create();

Here is the class (you’ll need to customize the $SERVERS array for your configuration — note that you would probably use the same username, password and database for all of the servers, just changing the host name, but you’re not forced to use the same ones):

// ‘myHost1′,
‘username’ => ‘myUsername1′,
‘password’ => ‘myPassword1′,
‘database’ => ‘myDatabase1′),
array(
‘host’ => ‘myHost2′,
‘username’ => ‘myUsername1′,
‘password’ => ‘myPassword2′,
‘database’ => ‘myDatabase2′)
);

public static function create() {
// Figure out which connections are open, automatically opening any connections
// which are failed or not yet opened but can be (re)established.
$cons = array();
for ($i = 0, $n = count(MySQLConnectionFactory::$SERVERS); $i //

Lightrains Technolabs

You would ONLY use this for queries, never inserts/updates/deletes, UNLESS you had a multi-master situation where updates to any database serverautomatically replicate to the other servers (I don’t know whether that’s possible with MySQL).

Using this class, you get a connection to a MySQL server like this:
$con = MySQLConnectionFactory::create();

Here is the class (you’ll need to customize the $SERVERS array for your configuration — note that you would probably use the same username, password and database for all of the servers, just changing the host name, but you’re not forced to use the same ones):

‘myHost1′,
‘username’ => ‘myUsername1′,
‘password’ => ‘myPassword1′,
‘database’ => ‘myDatabase1′),
array(
‘host’ => ‘myHost2′,
‘username’ => ‘myUsername1′,
‘password’ => ‘myPassword2′,
‘database’ => ‘myDatabase2′)
);

public static function create() {
// Figure out which connections are open, automatically opening any connections
// which are failed or not yet opened but can be (re)established.
$cons = array();
for ($i = 0, $n = count(MySQLConnectionFactory::$SERVERS); $i

Lightrains Technolabs

http://php.net/manual/en/mysqli.persistconns.php

And the potential gotchas of pconnect are all symptoms of bad design themselves: having far too many client processes (think mod_php); forgetting to unlock tables and not cleaning up temporary tables; poor use of session variables, etc.

I have been running a high-concurrency app on Apache with the worker mpm (up to 3000 threads), with fastCGI + PHP (1 process, 24 children), connecting to mysql via Unix sockets with persistent connections. I have not had any problems. Even if the benefits are small, there is no cost. Net win.

I have a Server Application (in-house) which in turn let’s a bunch of clients connect to it. These clients give feebdack.. A LOT of feedback, (think in terms of narrowcasting players which tell me what image they have played at what time and which screen.. such an image is displayed for 10 seconds and then goes to the next.. these are 8460 records per day per screen per player.. ). Next to this, they query data (are there new files, ads etc) and they log certain events..

Now i tryed doing this with the Mysql.NET connector and opening and closing the connection but up until now, i haven’t got this working yet.. so for now, i’m using a concurrent connection per client that is connected to my server. Performance has never been fantastic though.

So my question is: Per query connection of keep a concurrent connection per client that is connected ?