Bob Evans writes: > I'm starting simple, there is no app. > > I have a 10GB file (called foo) on the internal FC drive, I did a zfs create > raidz bar .... > then ran "cp foo /bar/", so there is no cpu activity due to an app. > > As a test case, this took 7 min 30 sec to copy to the zfs partition. I > removed the pool, formatted > a single drive, and then tried to copy the same file to a single drive that > was nfs mounted. > This only took 5 min 30 sec. > > Watching disk activity, it seems like I get 2-4 seconds of writes, followed > by 2-4 seconds of inactivity. > > Bob
That's points to the jumpiness issue. BTW, cp(1) is your application ;-) If it's not 100% on CPU then it's not your throttle, the storage is and _that_ should be busy 100% of the time. -r > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss@opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
