I'm trying to determine the "correct" way of
dealing with a high availability situation,
which might also be a high performance (spread queries
across multiple systems) situation.
I've "googled" for MySQL cluster, and found one
project that last seems last touched a year ago.
1) All data is rea
Sun 450
Solaris 7
3 CPU
MySQL binary install
50 million record table. Initially tested on dual
CPU Intel Linux, now trying on Sun.
During index create (via alter), it copies the base
file (as documented). It spins the CPU at about 31%,
with 7 threads active. There is almost NO iowait (fast
f
MySQL - spam bypasser
> myisamchk --keys-used=3D0 -rq
> You can enable/disable keys from command line in 3.23.
While that would disable the key before the load,
how do I re-enable them afterwards?
-
Before posting, please
I'm trying to understand the most efficient load sequence
possible.
I've got 2 large tables. Each is about 50 million rows,
taking about 20GB of disk space. My disk is accessed
via fibre channel, and can read/write about 40 MB per
second.
My system is a dual PIII 850, running Linux 2.4.2-2smp
