Hi all, I'm using a MyISAM table in a high availability environment as a rudimentary persistent FIFO queue. The table definition is simple - the key is an auto_increment unsigned bigint and the data is a blob (it holds the contents of a C structure with a length of 200-400 bytes). I've got a couple of daemon processes that do inserts into the table, one daemon that reads the earliest row from the table (min) in a loop, and multiple 'consumers' that do something useful with the data and then delete the row.
My questions revolve around what type (if any) maintenance I need to do and what pitfalls I may encounter. - What type of maintenance do I need to do on this table? How often? I can't really take the table out of service. It processes up to 500,000 inserts/deletes an hour. - Are there known problems with this type of usage (heavy insert/delete) with MyISAM files? What should I be looking for from a monitoring perspective? - Is there a recommended version I should be using? Is 4.0 okay for this? I am currently using 3.23.42 on a Sparc Solaris 8 built with gcc 2.93. Thanks in advance for any advice (provided that it's good, of course :) ). regards, Rick [EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
