On Aug 11, 2009, at 1:21 PM, Ed Spencer wrote:
Concurrency/Parallelism testing.
I have 6 different filesystems populated with email data on our mail
development server.
I rebooted the server before beginning the tests.
The server is a T2000 (sun4v) machine so its ideally suited for this
type of testing.
The test was to tar (to /dev/null) each of the filesystems. Launch 1,
gather stats launch another , gather stats, etc.
The underlying storage system is a Network Appliance. Our only one. In
production. Serving NFS, CIFS and iscsi. Other work the appliance is
doing may effect these tests, and vice versa :) . No one seemed to
notice I was running these tests.
After 6 concurrent tar's running we are probabaly seeing benefits of
the
ARC.
At certian points I included load averages and traffic stats for
each of
the iscsi ethernet interfaces that are configured with MPXIO.
After the first 6 jobs, I launched duplicates of the 6. Then another
6,
etc.
iostat and zpool iostat measure I/O to the disks. fsstat measures
I/O to the file system (hence the name ;-). A large discrepancy
between the two is another indicator of filesystem caching.
While tar is slightly interesting, I would expect that your normal
backup workload to show a lot of lookups and attr gets. If these
are cached, life will be better.
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
