Quoting Marvin Wright <[EMAIL PROTECTED]>: > Hi, > > It suggests below to bundle transactions into one commit, at what point does > this become unecessary ? > > For example I have 2 threads each doing 12,000 inserts in 1 commit each. > Would I really gain any performance if I did these 24,000 inserts in 1 > commit only ? >
I would not think this would make a difference, in fact you should test this, as it may be that in fact bundling 24,000 at a time is slower than 12,000 at a time. I know that things can slow down when doing too much in one transaction in Oracle for example, and InnoDB/MySQL might be similar. With regards to performance gains by bundling, this is more about not committing after one insert but committing after 10 or 100, as there will be certain performance gains here. > Additionally, what performance should I be able to acheive with innodb ? > My server is currently Linux RH, 2 CPU's 3.2Ghz, 4 Gig of ram and SCSI > drives. I think my queires are optimised, I've had as much as 8000-9000 > inserts per second but this is when I start to run into machine load issues. > Am I asking to much of the machine ? > Each platform/hardware/OS/etc. will have different performance than another, but I would think that you are doing pretty well at 8000-9000 inserts per second. With a dual CPU system, you could also try doing the inserts in parallel for further speed, for example in a 2nd forked or threaded job, so as to make sure the system is taking full advantage of that 2nd processor, otherwise a process that is executing serially/sequentially will just use up one CPU. When it comes to benchmarking & performance tuning, make sure to establish a level as which performance is good enough ahead of time, otherwise you can spend all your time doing these things with only marginal gains. Regards, Josh -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
