VBGamer

um, nothing wrong with what I said. PHP is the scriptor yes, MySQL is your DB, yes. I have news for ya :) MySQL can handle just about as many concurrent connects as an Access DB, which is 1024. I just looked it up to make sure I am not talking out of turn. That means about 100 people can stroke the DB at one time, given that each connection opens the min of 5 threads. A site with even moderate traffic, like 40-50 visitors between session timeouts (usually 20 minutes), would buckle under this strain. Remember this is not just the DB that is working, it is the server. The server has to serve the page, process a request, log the event, and spit it back to the user. Right there you have 3 threads open and running. Not to mention the other threads for serving graphics, standard html pages, etc... I am not saying PHP and MySQL is bad, just that it is not intended for major traffic. Then, you have to start thinking about other things. Is this site on a shared server? If it is, then that is even less it can process. 1024 is the limit for a pure server running only a single site. The server would have to be a very robust system (1 gig o ram) to handle multiple sites and serve the pages quickly, or reliably. I am not blowing smoke in the wind, we have done this for the last six years. It is my life staple. I am just pointing out that if anyone of us does start a site that has that much traffic pouring in, or potential traffic, should get the facts. There are plenty of links I have for MySQL, SQL 7.0/2K, CF, et. al. that discuss this very topic, a quick google search for +"mysql" +"concurrent connections" will reveal all that I have said.