in order to be able to use the replication features of MySQL we recently
gave version 4.0.1alpha a try, since these features are reportedly more
reliable in this version - although it is still alpha.
Unfortunately the disadvantages - at least on our machines - don't seem
to make up for the advantages: we experienced a very high server load
combined with higher memory-usage than usual, the average speed dropped
to a level the tested databases became almost unusable.

Let me explain our setup:
we're running a site-internal messaging system that handles approx.
110.000 messages per day. The databases consists of a header and a
content table, the first one being a fixed-length MyISAM-table with
almost 40.000.000 records, the second one is a dynamic-length
MyISAM-table with some 20.000.000 records. We don't use fancy stuff like
InnoDB but only very basic SELECT (on indexed columns) and INSERT
statements, not even JOINs.
The whole thing runs on a 850MHz dual-pentium with 4GB memory under
Linux 2.4.17 and RAID1.

Until now we used MySQL 3.23.32 which in our tests remains the fastest
version so far, all following versions (including 3.23.47 and
4.0.1alpha) remarkably dropped in speed.

Now finally to my question:
is there a way to speed up 4.0.1alpha (or any other version with
reliable replication), maybe a different OS (BSD is reported to be more
performant but we have no experience with that so far) could help? Are
there any fine-tunings in the ./configure that may have a positive
effect (we didn't notice big changes in speed and memory usage when
playing with these options)?

Usually we would just stick with 3.23.32 but, as mentioned above, we
need the slightly more advanced and reliable replication features of its
successors in order to be able to distribute read accesses to several
slaves while the master does all the writing stuff.

Any help/comments much appreciated

PHP Database Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to