In the last episode (Jul 01), Mathias said:
> Dan Nelson wrote:
> >In the last episode (Jun 30), Mathias said:
> >>We've been benchmarking a database that in real-life will have a
> >>huge write load (max peak load 1 inserts/second) to the same
> >>table (MyISAM).
> >>
> >>We will need about 4
Write to a memory table first then do a hotcopy on a scheduled basis.
Do you mean converting the memory table into MyISAM on a scheduled
basis? (mysqlhotcopy only works on MyISAM and ISAM tables). Or is there
a faster way of storing the table to disk?
- Mathias
We've been benchmarking a
Dan Nelson wrote:
In the last episode (Jun 30), Mathias said:
We've been benchmarking a database that in real-life will have a huge
write load (max peak load 1 inserts/second) to the same table
(MyISAM).
We will need about 4 indexes for that table. However, from our
benchmark tests, it
Subject: Possible to delay index writes until server is less busy?
We've been benchmarking a database that in real-life will have a huge
write load (max peak load 1 inserts/second) to the same table
(MyISAM).
We will need about 4 indexes for that table. However, from our
benchmark tests
In the last episode (Jun 30), Mathias said:
> We've been benchmarking a database that in real-life will have a huge
> write load (max peak load 1 inserts/second) to the same table
> (MyISAM).
>
> We will need about 4 indexes for that table. However, from our
> benchmark tests, it is clear that
Write to a memory table first then do a hotcopy on a scheduled basis.
- Original Message -
From: "Mathias" <[EMAIL PROTECTED]>
To:
Sent: Thursday, June 30, 2005 9:10 AM
Subject: Possible to delay index writes until server is less busy?
We've been benchmarki
We've been benchmarking a database that in real-life will have a huge
write load (max peak load 1 inserts/second) to the same table (MyISAM).
We will need about 4 indexes for that table. However, from our benchmark
tests, it is clear that writing indexes takes too many resources and
impede
