Re: asyncio-based ZEO implementation implemented

Christopher Lozinski <[email protected]>
Newsgroups gmane.comp.web.zope.zodb
Message-ID <[email protected]>

On Sunday, June 19, 2016 at 9:12:45 PM UTC+2, Jim Fulton wrote:
>
>
> This is a large pull request, so I get why nobody might want to review 
> it. 
>

So how does one review ZEO?  Well the first step is to understand 
FileStorage. 


I made some comments on the docs over on github issues, but here are some 
high level questions which should interest everyone. 


Let me ask the obvious question.  If the Python GIl prevents multiple 
threads from executing at the same time, 
why does filestorage use multiple threads?  Would it not be easier to just 
have a single thread. 


Answer: The problem is with the OS.  It blocks on writing to a file.   So 
it makes sense to have a separate thread 
for writing transactions on Data.fs and on the lock file. 


Question: So why does ZODB filestorage support multiple threads?  Is it so 
that every transaction gets its own thread with its own cache, and version 
of objects? 


Regards
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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.