3 ms·
So what was the CPU on that bottleneck, out of curiosity? If single core is the problem, throw a massive clock rate at it? The i5-680 is out this month and is
by ck2 17y ago
So what was the CPU on that bottleneck, out of curiosity?
If single core is the problem, throw a massive clock rate at it?
The i5-680 is out this month and is 3.6ghz native ("turbo" near 4ghz) should do 5ghz with good air cooling (it's 32nm) and then you could use ECC memory to be certain in a mission-critical environment?
- jzawodn 17y agoThis was... lemme see. less /proc/cpuinfo Intel(R) Xeon(R) CPU X5570 @ 2.93GHz So it was a pretty high-end Nehalem proc already. And, yeah, we do have ECC RAM in the box, of course. Plus InnoDB does page-level checksumming to guard against corruption too. But still, it was ~8 hours or so. Using all 8 cores on the box would have brought it down to ~1 hour if it could have been perfectly parallelized (and much of it could have been, I bet).
- ck2 17y agoAh okay, so even with the fastest clocks available today, the best you could hope for is cutting the 8 hours to 4, or one month to two weeks. As far as the parallel cores it sounds like you already have thought about possible "end runs" around MySQL's "transaction safe" ALTER (which is probably why it's single threaded). InnoDB supposedly has a few performance improvements for ALTER over MyISAM so you are already taking advantage of that.
- soundsop 17y agoMemory ECC won't help if computations are incorrect.
- pyre 17y agoGood computations won't help if your memory is corrupt.
- reitzensteinm 17y agoThat's not what soundsop was saying - he was just pointing out the obivous error in the suggestion to overclock the CPU, and then use ECC to be safe. The ECC, though a good idea by itself, will not help with any errors introduced by the overclock.