Archive Table about logblock HOT 4 CLOSED

If it's the inserts, not the reads, that are lagging, will they not also lag when inserted into the archive table? Or do you plan to not index them (meaning very high read lag)?

from logblock.

No, but using some kind of bulk insert (several thousand rows at once), that should help to create the indices faster.

from logblock.

It's true this will get the table's SELECTions alot faster with alot smaller indices and smaller table, but after all a regular SQL table is designed to contain any amount of data and still be reasonably fast, especially on MySQL. Take our Mainworld table for an example, it has over 33 million rows and SELECT was always fast on one engine and so much faster on second. I grant that a table with 33k rows is faster than 33 million, but in the end with proper conf you won't mind 2-100ms slower SELECT.

But, like I've read, moving shit from a table to archiving table is wasting of all with proper-like table and index design. LB's block change table indexing is about as perfect as it can get by my experience, so slow SELECT or INSERT comes from totally wrong conf.

from logblock.

As we have bulk inserts in the main table now, I don't think there is a reason for an additional archive table

from logblock.