persistant mysql connection

[AlbertAguirre]

I am working on a project where the mysql database is located on a separate physical server from the web sever.

I notice sometimes when retrieving records that it takes an extended amount of time (7 seconds or so) to display the results (30 records or so, small table)

I know for a fact it is not the table or datase. My guess is that when making the remote connection to the db via ip addr, network traffic may be affecting it.

Will a persistant connection solve this problem?

 

[sleipnir214]

Perhaps. But it seems to me that you must have traffic problems on that network link. Besides the web and database servers, what's on that network?



Want the best answers? Ask the best questions! TANSTAAFL!

 

[AlbertAguirre]

Hundreds of servers, systems.. This is a large operation.

but still this wont affect db queries. because of the network traffic my connection time seems to slow down.

So my guess is a persistent connection will allow a one time slow down then normal speed after?

Also, with persistent connections, does this mean the user connects ONCE to the db then no matter how many pages he visits that connect remains established?

 

[sleipnir214]

As a nearly universal standard configuration, when I have separate database and web servers, I make sure that those connections (between the web and database servers) are on a separate network. It cuts down a lot on network lag (particularly if you have a lot of Microsoft machines running Microsoft's broadcast-chatty protocols).



Want the best answers? Ask the best questions! TANSTAAFL!