Re: Performance question when clustering

[Patricio Echagüe]

It might be a late reply but we i saw at least in JR 2.0 is that when
session.save() happens it also forces a sync first so that the JR node gets
up-to-date first.

We also see the degradation in performance the more nodes we put in the
cluster. The global lock forces to make every session.save() sequential
since it acquires a global lock.

My 2 cents

On Tue, Apr 20, 2010 at 4:49 AM, Thomas Müller thomas.muel...@day.comwrote:

 Hi,

  automatic sync and the manual Session.refresh() have essentially the
  same result?

 I think so.

  Should this be something you should know?

 I don't plan to find out, sorry. I didn't write the cluster code, and
 I don't feel responsible for it :-)

 Regards,
 Thomas




-- 
Patricio.-

Re: Performance question when clustering

[Thomas Müller]

Hi,

 automatic sync and the manual Session.refresh() have essentially the
 same result?

I think so.

 Should this be something you should know?

I don't plan to find out, sorry. I didn't write the cluster code, and
I don't feel responsible for it :-)

Regards,
Thomas

Re: Performance question when clustering

[Thomas Müller]

Hi,

The automatic sync is periodic (once every few seconds).
Session.refresh() will force an immediate cluster sync. I'm not sure
if the immediate cluster sync on Session.refresh() is a good idea, but
that's how it's implemented currently.

 - Why is a refresh more expansive when there are more cluster nodes?

This I don't know.

Regards,
Thomas