Richard Elling wrote: > Michael Schuster - Sun Microsystems wrote: >> Sean Meighan wrote: >>> I am not sure if this is ZFS, Niagara or something else issue? Does >>> someone know why commands have the latency shown below? >>> >>> *1) do a ls of a directory. 6.9 seconds total, truss only shows .07 >>> seconds.* >> >> [...] >> >> this may be an issue with your $PATH. Do you see the same behaviour if >> you use absolute paths for the commands? > > It could also be an interaction with your shell. ksh, for example, will > write to your $HISTFILE before the exec. If it takes a long time to > update your $HISTFILE, then it will appear as if the command itself is > slow. truss -d on the shell will show this conclusively.
ksh doesn't just write to $HISTFILE - ksh fsync()s it, and thus one may be tripping over: 6413510 zfs: writing to ZFS filesystem slows down fsync() on other files in the same FS Certainly, I initially found this issue as a result sluggishness in the ksh prompt. Dana _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
