Mathieu Bruneau <[EMAIL PROTECTED]> wrote:
> > BTW, here's another oddity I noticed - here's typical output from
> > "iostat 60":
> > 
> > | avg-cpu:  %user   %nice    %sys %iowait   %idle
> > |            7.35    0.00    3.59    0.94   88.12
> > | 
> > | Device:            tps   Blk_read/s   Blk_wrtn/s   Blk_read   Blk_wrtn
> > | sda              29.20         8.00       342.08        480      20528
> > | sda1              0.00         0.00         0.00          0          0
> > | sda2              0.00         0.00         0.00          0          0
> > | sda3              0.00         0.00         0.00          0          0
> > | sda4              0.00         0.00         0.00          0          0
> > | sda5             43.74         8.00       342.08        480      20528
> > | sdb               2.43         0.00       173.70          0      10424
> > | sdb1             21.71         0.00       173.70          0      10424
> > 
> > I've been running this for a few hours and it consistently shows lots
> > of writes but no reads at all on sdb1, the partition where I have my
> > binary logs and tmpdir.  Is MySQL writing lots of tmp files and not
> > reading them?  Or, how else can I interpret this?
> 
> The binlog are creating most of your constant write most probably. If
> you have no slave attached, you're not reading them at all...

Yes and no.  In fact, this iostat output comes from a slave, where
there's hardly any binglog activity (but a fair amount of relay log
activity).  However, I noticed the same thing on the master.  Before
tmpdir pointed to a directory on sdb1, there was a much lower, and
fairly constant, level of writes to that partition, which did not
surprise me.  After I pointed tmpdir to sdb1, the amount of write
activity grew substantially and started varying much more (from as low
as ~50 to as high as ~400), but I still see no reading recorded.
  -- Cos

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to