Brent Baisley wrote:
> Well, there is the ideal setup, which requires intimate knowledge of the
> database, lots of disks and extra administration. And then there is the
> easy setup. Ideally you don't want to have any "hot" disks which will
> cause contention. This requires you to place your bu
Well, there is the ideal setup, which requires intimate knowledge of the
database, lots of disks and extra administration. And then there is the
easy setup. Ideally you don't want to have any "hot" disks which will
cause contention. This requires you to place your busy tables (read or
write)
Hi,
In my experience (assuming that you are using mysql for all of these
operations) the best way is to separate your tables into read-heavy and
write heavy and put each into separate databases. Put the write-heavy logs
database onto a separate disk/spindle and use delayed inserts (so that the
a
