Re: [infinispan-dev] ClockService
On 1/29/13 7:25 PM, Mircea Markus wrote:
On 29 Jan 2013, at 16:25, 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.
>
> Having it as a service we will be able to experiment: the first thing
> I'll do is replace it with a NOOPService and see how much it improves.
That should be the first step IMO. No point in trying to start
optimising before we know this is a performance problem :-)
+1000. There's probably more low hanging performance fruit in Infinispan
to be tackled...
--
Bela Ban, JGroups lead (http://www.jgroups.org)