On Jan 5, 2007, at 6:08 PM, Jonathan Vanasco wrote: > for small stuff, not a problem. for large stuff, i think it is -- > which is why i'm a little shocked at the original poster. i'd be > scared shitless to be dealing with an 18M row mysql db myself.
5+ years ago I worked at a place with many tables you would consider "large". Even MySQL 3.x worked quite alright with that. On a newer project we have a bunch of 18M+ row tables - larger ones too. We don't have anyone dedicated to maintaining them. It Just Works. Sure, we've tuned buffer sizes and such a bit to use the hardware properly, but you always have to do that, no? We haven't launched our site yet, so the database servers aren't really busy yet, but the processes we have loading and moving data around still regularly do 500-1k QPS in a mix of selects, inserts and updates. (And last I checked that was limited primarily by the box the applications were running on ...) - ask -- http://develooper.com/ - http://askask.com/ ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Rose-db-object mailing list Rose-db-object@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/rose-db-object
