Francisco wrote:
On Mon, 5 Sep 2005, Chuck Swiger wrote:
Small writes are pretty much the worst-case scenario for RAID-5,
Such as mail servers?
So-so. RAID-5 is okay on a IMAP reader box, it's not so good for a pure SMTP
relay, especially one that does virus scanning.
How about for a DB
> Is there a way to find out which program(s) are causing
> the I/O?
ktrace(8); you can use it to trace all descendants of 'init'.
--
FreeBSD Volunteer, http://people.freebsd.org/~jkoshy
___
freebsd-performance@freebsd.org mailing list
http://lists.
Francisco Reyes wrote:
On Tue, 13 Sep 2005, mariano benedettini wrote:
91.3% idle
CPU is not the problem. :-)
Mem: 1599M Active, 1704M Inact, 311M Wired, 189M Cache, 112M Buf, 14M
Free
Swap: 2023M Total, 184K Used, 2023M Free
Swap is not the problem.
Do
vmstat 10
Watch the output.
Looking at vmstat I see the "b" colun never hits zero and it's usually
between 5 and 20.
Is there a way to find out which program(s) are causing the I/O?
In some of the machines it was near trivial to find the culprit, but have
a handfull of machines that I am not sure what the cause of I/O is
On Tue, 13 Sep 2005, mariano benedettini wrote:
91.3% idle
CPU is not the problem. :-)
Mem: 1599M Active, 1704M Inact, 311M Wired, 189M Cache, 112M Buf, 14M Free
Swap: 2023M Total, 184K Used, 2023M Free
Swap is not the problem.
Do
vmstat 10
Watch the output.
In particular look at the f
