Ignore my request. Even if there was a way to clear an array, there
is no function that allows me to print out that array. Only an
aggregation does that.
True, and I'd argue that an aggregation is probably the right data
structure
for what you're doing.
Adam
--
Adam Leventhal,
Marcelo Leal wrote:
Marcelo Leal wrote:
Hello all...
Thanks a lot for the answers! I think the problem
is almost fixed. Every dtrace documentation says to
use predicates to guarantee the relation between the
start/done probes... Max was the only one paying
attention reading
Marcelo Leal wrote:
Hello all...
Thanks a lot for the answers! I think the problem
is almost fixed. Every dtrace documentation says to
use predicates to guarantee the relation between the
start/done probes... Max was the only one paying
attention reading the docs. ;-)
Actually,
Marcelo Leal wrote:
Hello all...
Thanks a lot for the answers! I think the problem is almost fixed. Every
dtrace documentation says to use predicates to guarantee the relation between
the start/done probes... Max was the only one paying attention reading the
docs. ;-)
Actually, this
I think (us) is microseconds. There is one division by 1000 on the source
code...
Leal
[http://www.eall.com.br/blog]
--
This message posted from opensolaris.org
___
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
Hi Marcelo,
Marcelo Leal wrote:
I think (us) is microseconds. There is one division by 1000 on the source
code...
Oops. You're right. I did not see that. (That might explain
the 4-8 nanosecond I/Os, which I did think seemed pretty fast.
They are actually 4-8 microsecond). So, you want
Hi Marcelo,
Marcelo Leal wrote:
Ok, but that is a bug, or should work like that?
We can not use dtrace on multiple processors systems?
Sorry, but i don't get it...
I don't consider this a bug. I think it depends on what you are trying
to measure.
The script you are using measures
Sorry, but i do not agree.
We are talking about a NFSv3 provider, and not about how many cpu's there are
on the system. I do not have the knowledge to discuss with you the aspects
about the implementation, but as a user point of view, i think that numbers
don't make sense. If the fact that the
No bug here - we can absolutely use DTrace on MP systems,
reliably and with confidence.
The script output shows some nasty outliers for a small percentage
of the reads and writes happening on the server. Time to take a closer
look at the IO subsystem. I'd start with iostat -znx 1, and see what
On 12/11/08, Paul Clayton [EMAIL PROTECTED] wrote:
Next up is other mechanisms to get FPU info.
So I go searching the web and find Darryl Gove's web page of
http://blogs.sun.com/d/entry/using_dtrace_to_locate_floating that talks to
using kstat and dtrace to look for 'fpu_unfinished_traps'.
Rayson..
My thanks for the pointers to the two documents. Very interesting
reading.
For the emulated instructions, I now have my answers to tell what is
happening. In the case currently under investigation the only emulation
is FSQRTD and that stands at 884K but is not currently growing so
11 matches
Mail list logo
