On Tue, Nov 04, 2003 at 08:45:08PM -0500, Jonathan Terhorst wrote: > > I could have sworn I posted this once before, but apparently it got > lost somewhere. Apologies if you're seeing this twice: > > I'm wondering what I can do with MySQL to optimize reads (SELECTs) > on a read-only table where data will never be INSERTed or > UPDATEd. Okay, that's not entirely correct--the database will be > rebuilt every night but it's small (~20,000 rows) and all the > writing will take place at once, when the DB is offline to users. In > contrast we anticipate read activity on the DB to be high, making it > worth putting some thought into this. So far my only thoughts have > been a) myisampack and b) to index every single column that our > application searches on, since the calculations needed to build said > indices can be performed once and forgotten. (Disk space isn't > really an issue but myisampack is said to speed up individual row > retrieval.) > > Any other ideas? I've searched for a way to manually mark MySQL > tables read-only, but to no avail. Thanks,
Will the whole table fit comfortable in RAM? If so, you could store it in a ram disk to prevent disk I/O from ever getting in the way. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.15-Yahoo-SMP: up 56 days, processed 2,111,575,079 queries (434/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
