MySQL Forums
Forum List  »  Partitioning

Re: Partitioning help
Posted by: Rick James
Date: September 27, 2010 07:55PM

Eh? 1000 HTML inserts/hour & 10GB/hour -- is each HTML page 10MB? That is huge! If 99% of the data is that column, there won't be that much difference is size between MyISAM and InnoDB.

1000 Inserts/hour -- yawn. No need to batch INSERTs if they are that infrequent.

10MB inserted in 50ms -- that's tight. Fortunately, there can be a lot of "write caching", so it may be possible.

Do the compression in the application, not mysqld; that will help spread the load around. (Compression is CPU intensive, but saves a lot in I/O.)

You have not mentioned any SELECTs, so the only criteria for PARTITIONing is the DELETE. So, PARTITION date. Don't bother partitioning on `type`.

MyISAM or InnoDB could handle it -- you have not provided any requirement that shouts for one over the other.

If you use MyISAM, be sure to provide a large value for MAX_ROWS in the CREATE TABLE statement.

What will the SELECTs be? It may be advisable to "vertically partition" as well.

JMS queue? Sounds like something that will slow you down.

Options: ReplyQuote

Written By
September 24, 2010 02:16AM
September 25, 2010 01:09PM
September 27, 2010 03:43AM
Re: Partitioning help
September 27, 2010 07:55PM
October 12, 2010 01:55AM
October 12, 2010 08:03AM
October 13, 2010 03:27AM
October 13, 2010 06:03PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.