The answer (like most of these) is, "it depends". You really need to
benchmark your application to know how often a "user" is going to
actually hit your database server, and how many connections the
application creates for each user. I've got a server that handles the
databases for 3000 users hitting web apps on several different web
servers without blinking (dual P4 Xeon, 2 GB of memory). It runs at
worst 75% idle. On the other hand I've seen applications where 100 users
would bring this server to it's knees if it were serving the database
for it. It all depends on usage and you can't get from "users" to
"database usage" directly.
I would pile up some hardware your not using at the moment set things up
and write some scripts to simulate actual usage of your application.
Load the server with some real data, especially in terms of quantity of
rows, and see what it handles. Measure performance and system usage
metrics and go from there.
--
Michael Conlen
NEWMEDIAPLAN wrote:
Can mysql handle 5000 concurrent webusers sending queries to the db through
a web search engine.
Is it possible (with a very big server/hw) ?
Thanks. Roberto
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
