On 04/17/09 21:19, Kyle McDonald wrote:
> One reason is that you're not timing how long it takes for the destroy's
> to complete. You're only timing how long it takes to start all the jobs
> in the background.
Right, I'm sorry, my example was an oversimplification of a script I made.
That script included a wait after the for-loop. The same example again:
# date ; for i in `zfs list | awk '/blub2\\// {print $1}'` ; \
do ( zfs destroy $i & ) ; done ; wait ; date
Yields
Fri Apr 17 22:56:32 UTC 2009
Fri Apr 17 22:56:40 UTC 2009
Still 8 seconds total, including waiting for all the "zfs destroy"s to
complete. I can't tell whether the kernel is post processing any of the
destroys after the zfs command exits, but that's true for the "destroy -r"
case as well, and that still takes 38 times as long.
Joep
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
