search for: lquantize

...END are not recorded 6311958 should indicate missing jstack() frames due to string table overflows 6311960 allow some DTrace options to be set dynamically 6311963 jstack() produces stacks packed with "StubRoutines" 6311975 allow boolean DTrace options to be unset 6315028 allow quantize()/lquantize() increments to be D expressions 6315033 add dtrace_addr2str()/dtrace_uaddr2str() to libdtrace API 6315034 add ucaller variable 6315035 enablings containing USDT probes are not dynamically reevaluated 6315037 cannot aggregate on the return value of some subroutines 6315039 including <sys/kstat.h...

Hiya, I''m trying to track down some throughput latency that our customer seems to be attributing to our product, I can''t see what he''s talking about, but I want to try and get some deeper granularity than I might get with something like smokeping, and maybe even see if its down to something tunable on our end. I''ve been looking for some examples on how

When somebody is hammering on the system, I want to be able to detect who''s doing it, and hopefully even what they''re doing. I can''t seem to find any way to do that. Any suggestions? Everything I can find ... iostat, nfsstat, etc ... AFAIK, just show me performance statistics and so forth. I''m looking for something more granular. Either *who* the