Re: Mass Import Innodb
Posted by:
Rick James
Date: February 07, 2012 10:38AM
> 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.
Subject
Views
Written By
Posted
3782
January 29, 2012 07:10AM
1179
January 30, 2012 09:07AM
1163
January 30, 2012 10:24AM
1108
January 31, 2012 07:06AM
1090
January 31, 2012 02:51AM
1072
January 31, 2012 03:21AM
1141
January 31, 2012 10:20AM
1367
January 31, 2012 10:44AM
1058
February 01, 2012 02:22AM
1185
February 01, 2012 04:33AM
1124
February 06, 2012 05:59AM
Re: Mass Import Innodb
1270
February 07, 2012 10:38AM
1138
February 07, 2012 11:15AM
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.