Re: Central cache for ZEO Clients

On 2/4/16 11:33 AM, Rene´ Jochum wrote:
> Is this something ZODB and the community needs?
I think so.

The huge unanswered question is why are ZEO clients slower than
RelStorage clients.  They are running so much
less software, they should be faster.  Presumably the answer is because
Relational databases have a more advanced
caching strategy.  I think that if you could make ZEO clients perform as
fast as RelStorage clients,   developers would
choose ZEO over RelStorage.  I would certainly prefer to manage a ZEO
server over a RelStorage Server.

When I was at the Plone conference I talked about this issue with one
person.   I wish I could be more exact in my feedback.

The documentation on all of this is not very clear.  I must have read
literally every zodb blog out there
for blogory.org/zodb
and I am still not sure how it all works.

I think that every thread has its own object cache, so the same object
can be cached multiple times on one machine.  Maybe it makes more sense
to have only one cache of the object on a client machine.  But I am not
sure about all of this.

So my first recommendation would be to write up what is, and then write
up what you want to do.
That would make it a lot easier for people to give you feedback, and
advice, and get engaged.

Google Docs is great for this purpose.  I think it would be very
interesting to meet on-line, discuss these ideas, and write up a
proposal. 

Chris

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.