Hi Raj, Ananda, the schema is very simple, we don't have any blob or text
column.
I thought the same about the log files, so I tried with diferent sizes but
nothing change.
This is the output of iostat -x 1 when the performance is slow running a
restore
avg-cpu: %user %nice %system %iowait %
How big is your /tmp folder, can u move this to other fast moving disk.
On Fri, Mar 19, 2010 at 4:27 AM, Raj Shekhar wrote:
> Max Bube gmail.com> writes:
>
>
> > The problem starts when I run bulk writes like an alter table or a
> restore
> > from mysqldump, its starts processing more than 5000
Max Bube gmail.com> writes:
> The problem starts when I run bulk writes like an alter table or a restore
> from mysqldump, its starts processing more than 5 rows/s but suddenly
> the ratio goes down to 100 rows /sec. and then its stucked at this ratio
> even if I restart MySQL. The only way
This is an output from console when its performnace goes dows
Query OK, 65469 rows affected (0.82 sec)
Records: 65469 Duplicates: 0 Warnings: 0
Query OK, 65469 rows affected (0.78 sec)
Records: 65469 Duplicates: 0 Warnings: 0
Query OK, 65469 rows affected (10 min 57.30 sec)
Records: 65469 D
when the writes are happening, please run "show full processlist" and let us
know the out put.
regards
anandkl
On Thu, Mar 18, 2010 at 9:09 PM, Max Bube wrote:
> Hi list,
>
> Im having problems with bulk writes (restores from mysqldumps, alters,
> delete in (select ...)) with innodb. The server
Hi list,
Im having problems with bulk writes (restores from mysqldumps, alters,
delete in (select ...)) with innodb. The servers are at amazon EC2 instances
w/ 15G ram and raid0 4disks EBS.
The problem starts when I run bulk writes like an alter table or a restore
from mysqldump, its starts proces
