On 5/30/2013 8:30 AM, Dotan Cohen wrote:
On Wed, May 29, 2013 at 5:37 PM, Shawn Heisey <s...@elyograg.org> wrote:
It's impossible for us to give you hard numbers. You'll have to
experiment to know how fast you can reindex without killing your
servers. A basic tenet for such experimentation, and something you
hopefully already know: You'll want to get baseline measurements before
you begin testing for comparison.
Thanks. I wan't looking for hard numbers, but rather am looking for
what are the signs of problems. I know to keep my eye on memory and
CPU, but I have no idea how to check disk I/O, and I'm not sure how to
determine even if that becomes saturated.
On UNIX platforms, take a look at vmstat for basic I/O measurement, and
iostat for more detailed stats. One coarse measurement is the number of
blocked/waiting processes - usually this is due to I/O contention, and
you will want to look at the paging and swapping numbers - you don't
want any swapping at all. But the best single number to look at is
overall disk activity, which is the I/O percentage utilized number Shaun
was mentioning.
-Mike
