When are you beating on MYSQL

[Fritz]

I have most of our site's more dynamic content in one Database... representing about 30 tables... with near 100 meg of data... would it be wiser to split this out to a few databases or can mysql handle this without a problem.

Basically I'd love some thoughts from some folks that dealing with this kind of data/traffic... It's also worth noting that PHP select calls per day are running around 240,000. Amazingly performance is still quite good.

any thoughts or links related to schema or personal experience would be very much appreciated.

[ultraslacker]

I've had performance problems with mysql on 100+ queries per second - due to table locking issues (myisam tables).

Keep it as one database. As a read only database (which sounds like what you have) mysql is very fast, and 100 megs is small enough to be kept in memory.

[Fritz]

Thanks for this reply... looks I have still have some headroom to beat on these tables.

thanks much