On Mar 26, 2007, at 6:55 PM, Marc G. Fournier wrote:
45 processes: 1 running, 44 sleeping
CPU states: 0.0% user, 0.0% nice, 0.4% system, 0.4% interrupt,
Mem: 35M Active, 285M Inact, 271M Wired, 44K Cache, 111M Buf, 402M
Swap: 2007M Total, 2007M Free
I just did:
mdconfig -a -t malloc -s 200m -o reserve
Now, my understanding, this builds a file system 'in core', vs on
the disk ...
with memory being faster then disk, I would have assumed that read/
performance would have been better, but, using iozone, I'm not
of a difference in performance to understand why I'd want to use a
In order to do useful disk benchmarks, you've got to perform I/O on
large enough files that they don't fit into RAM. If you've got 400-
odd MB completely unused according to top, you'd really like to use
at least 1-2 GB worth of file data. Of course, trying to do I/O
tests on a RAM disk means that you want the data to fit into RAM
without swapping, which then means that trying to do identical
testing between disk and RAMdisk doesn't really work too well.
email@example.com mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"