tag:blogger.com,1999:blog-7006618857347978140.post2325955722343058825..comments2010-07-16T09:47:20.096-07:00Kevin Lawtonhttp://www.blogger.com/profile/03442192017196947120noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7006618857347978140.post-44652713313762796212009-07-23T02:47:41.282-07:002009-07-23T02:47:41.282-07:00Like as if somebody haven&#39;t knew that already...<br /><br />As my SC teachers have said &quot;the programming is an art of resource management.&quot; Or like I put it now &quot;the resource management is a bitch.&quot;<br /><br />My point here is that automated resource management - especially in higher-end application market - would never ever be as efficient as traditional manual resource management.<br /><br />Additionally, if you take it to the NUMA systems (which are the cheap boxes with 8+ CPUs (not cores)), excessive memory consumption of Java also starts weighing in. On NUMA systems memory is generally slower. Meaning that more memory application consumes, slower it is.<br /><br />More cores/CPUs/threads trigger so-called &quot;cross traffic&quot; (CPU cache flushes to maintain coherency; RAM content transfer between NUMA nodes) slower the whole system becomes. And Java&#39;s GC has to have extra threads (accessing the very same memory as other threads running on different CPUs/cores) meaning that you can&#39;t avoid/minimize the cross traffic.Ihar Filipauhttp://www.blogger.com/profile/05086565400407007423noreply@blogger.comtag:blogger.com,1999:blog-7006618857347978140.post-44979712288858496562009-07-20T03:47:35.618-07:002009-07-20T03:47:35.618-07:00This comment has been removed by a blog administrator.cl333rhttp://www.blogger.com/profile/08999495801517077202noreply@blogger.com