The T5440 is at the extreme end of T-series NUMA latency. The T5220,
being just one chip, is at the other. Do you have all your vcpus in
one domain? If so, that's a lot more cross calls too! Very few apps
can scale sensibly on that beast and cope with both factors. I guess
DTrace is one of them.
Phil
Sent from my iPhone
On 20 Feb 2010, at 09:25, Ryan Johnson <ryanj...@ece.cmu.edu> wrote:
Hi all,
We just got a shiny new T5440, and one of the first things I noticed
(besides the insane number of hardware contexts), is that dtrace
takes 30 seconds to a minute to fire up scripts with 5-6 probes,
where our T5220 usually takes under a second. Shutdown is similar,
though slightly faster.
This is mostly annoying because it takes so long to attach that it's
hard to tell when I've collected enough data to be useful. I've
started using BEGIN and END probes to prun stopped instances of
'echo' so I can see when probing actually starts and ends...
Any idea why this should be the case? I'm running S10 (142900-03).
Thanks,
Ryan
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
_______________________________________________
dtrace-discuss mailing list
dtrace-discuss@opensolaris.org
