On 29 Jan 2013, at 17:17, Bela Ban <[email protected]> wrote: > > On 1/29/13 5:25 PM, Sanne Grinovero wrote: >> Glad you started work on that :) >> >> Any currentTimeMillis() even today will blow away your cache line and >> probably trigger a context switch. > > I understand the context switch (in general, it's not recommended anyway > to invoke a system call in synchronized code), but I fail to see why > this would blow the cache line. Are you referring to the cached Date > value here ?
No, if you have a separate maint thread that updates a reusable currentTimeMillis value. Do you use nanoTime() a lot then? Because that too is inefficient (as per the Oracle blog) ... -- Manik Surtani [email protected] twitter.com/maniksurtani Platform Architect, JBoss Data Grid http://red.ht/data-grid _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
