On Wed, 11 Apr 2012, Richard Lowe wrote:
cputrack is likely to be causing some of that impact.
The command is giving you I$ misses in general, I$ misses that hit in
L2, and I$ misses that went to memory. Given that apparently
bulldozer shares the I$ to some degree
What's plockstat -a showing? (all events, not just contention).
I get (from 'plockstat -A')
plockstat: processing aborted: Abort due to drop
I'm not sure blaming the allocator is fair (for a start, it's
behaviour would not differ between CPU revisions, so regardless of
fault, we're doing something pessimal to that CPU, based on what
you've said).
Right. And I should mention that the allocator is not consistently
listed as the top consumer. The top consumers depend on the algorithm
selected.
Bob
--
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/
-------------------------------------------
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
