Re: Mass Import Innodb

[Rick James]

> It is not a dedicated mysql server.
Get another server. Have just MySQL on one server (the one with the faster disks), and everything else, including all clients of MySQL on the other server.

That will cut down on disk contention. Notably, it will move some of the disk reads into network operations.

Face it, disk I/O is probably your bottleneck. Anything you can do to avoid I/O should be looked into:
* 2 machines (above)
* compression (fewer blocks -> less I/O) (already discussed)
* which operations to use (INSERT SELECT, etc)

If you get a second machine, then it would be better to use compress/uncompress in your clients, not in the database. This will offload more stuff -- CPU and network.

I'm puzzled -- You are concerned about "loading" time. What happens later?
* You will continue with heavy loading -- this will lead to terabytes of data?? Or you will need to DELETE lots of rows?? If DELETE by date, then you should be PARTITIONing.
* Won't you eventually need to SELECT the data? Shouldn't we be discussing that, too?

DELETE and SELECT hit the disk, too.