[ale] mysql advice

[Jeff Hubbs]

Any "major dude" RDBMS - and MySQL certainly is one - ought to be able 
to take 200 client connections at once.  I don't know for certain if 
there is a hard limit or what guides a practical limit, but it's a fair 
bet that plenty of RAM and a >$5 NIC are in order.  Laying out the 
server's drives intelligently would also be smart; I can't tell you how 
many times I've seen an entire DBMS' filesystem just dropped into a 
single hardware RAID5 array.

In MySQL, IIRC, tables map to individual files.  MySQL will have the job 
of sorting out how your multiple write queries to the same table become 
writes to the same file and because of that, write cache will matter.  
Some filesystems (e.g., ext4, JFS) may work better than others. 

I wouldn't so much worry about simulating per se as I would having a way 
to "dynamometer" various configurations.

Good luck with this; sounds like fun work!

- Jeff

Atlanta Geek wrote:
> We have an application that has about 20 daemons on a single server
> writing data to a mysql database.
> A new requirement has popped up that suggests we need 200 daemons on
> multiple servers writing data to a mysql database.
>
> Does anyone know if there is a client limit to mysql. Currently these
> daemons will be writing to the same tables. Any suggestions.  This
> situation is difficult to simulate in the lab unless we write
> speciallized code.  Any suggestions from experience would be
> appreciated.
>
>
>