Sean Meighan wrote:
i made sure path is clean, i also qualified the paths. time varies
from 0.5 seconds to 15 seconds. If i just do a "timex pwd", it always
seems to be fast. We are using csh.
Here's a simple dscript to figure out how long each syscall is taking:
#!/usr/sbin/dtrace -FCs
s
i made sure path is clean, i also qualified the paths. time varies from
0.5 seconds to 15 seconds. If i just do a "timex pwd", it always seems
to be fast. We are using csh.
itsm-mpk-2% env
HOME=/app/canary
PATH=/usr/bin:/usr/local/bin:/usr/sbin
LOGNAME=canary
HZ=100
TERM=xterm
TZ=US/Pacific
SH
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
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 is
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 beh
