> Different application algorithms show different high-runners but the > high-runner locks are usually > not called very often but are held for an abnormally long time. For some > algorithms the high-runners are in libc (e.g. malloc) and OpenMP but in some > others it is my application's explicit locks. >
Based on something Hans mentioned, something approaching: cputrack -c PAPI_l1_icm,PAPI_l2_ich,PAPI_l2_icm <your application> Could be useful in comparison to a system on which this doesn't occur (a synthetic test case would be better, I'm not sure these counters would be so useful under the real workload). There's also the DTrace cpc provider, but I can't currently come up with a good way to make use of it for what we'd want to know. -- Rich ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
