On 04/02/2012 12:34 PM, Pekka Enberg wrote:
On Wed, Mar 21, 2012 at 12:18 AM, Rik van Riel<riel@xxxxxxxxxx> wrote:
I suspect Java and other runtimes may have issues where
they simply do not know which thread will end up using
which objects from the heap heavily.
What kind of JVM workloads are you thinking of? Modern GCs use
thread-local allocation for performance reasons so I'd assume that
most of accesses are on local node.
Yes, the use thread-local allocation.
However, I suspect that after the memory has been allocated
locally, it may quite often end up with another thread for
further processing...
The JVM doing the right thing only helps so much, when the
Java program has no way to know about underlying things,
or influence how the threads get scheduled on the JVM.
Allowing us to discover which threads are accessing the
same data, and figuring out what data each thread uses,
could be useful for NUMA placement...
I have some ideas on how to gather the information that
Andrea is gathering, with less space overhead. I will
try to present that idea today...
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>