On Fri, 4 Nov 2011 16:49:02 +0600
Tair Sabirgaliev <tair.sabirgaliev@bee.kz> wrote:
> Sorry for replying to my own message! I'm very novice not only in PG
> but in using
> mailing-lists also..
Everybody needs a beginning :)
> > On Thu, 3 Nov 2011 00:05:58 +0600
> > Таир Сабыргалиев <tair(dot)sabirgaliev(at)bee(dot)kz> wrote:
> >
> >> We monitor the IO, and it never goes higher than 10MB/s, whereas the total
> >> throughput of DB disks is ~200MB/s.
> >
> > This isn't normal: it should be around 190MB/s.
>
> Do you mean that my real throughput is actually lower that what I've measured?
> Anyway I don't think the warning is a result of too high IO
No, I was only ironic (toward w$) - the problem you face isn't very easy to
fix because w$ lacks *nix usual tools.
You should search the web for such tools (iotop, analyse system i/o, etc) in
order to be able to identify which program(s) is creating this disk flow.
At first you could take a look into taskmgr: may be the program is using
some CPU resource and you'll be able to identify it while it writes to the disk.
--
"I'd love to go out with you, but I'm converting my calendar watch from
Julian to Gregorian."