Re: Re: overhead of ZEO connection
Jim Fulton <[email protected]>
| Newsgroups | gmane.comp.web.zope.zodb |
|---|---|
| Message-ID | <CAPDm-FjGOMj6mxEBrbwmJ3TwBa+HP+QvanYSTe6PTiG4VPjKqw@mail.gmail.com> |
On Wed, May 11, 2016 at 9:39 AM, Sanjay Rao <[email protected]> wrote: > Thank you very much and fully understand your explanation given here. To > take care of GIL issue I have divided my application into multiple processes > or more precisely you can say that multiple zope instances. > Now each zope instance can have multiple connections. > In this case I want to make sure that my ZEO wont become the bottleneck in > the system. Do you understand that ZEO connections and ZODB connections are completely different? The bulk of this thread has been about ZODB connections, *not* ZEO connections. A ZEO connection is made per process and database. You shouldn't change this. Multiple ZODB connections are made per process, typically one per application thread. Web applications typically make a connection per request. Because of the GIL, you should stop adding threads once you're typically using a high percentage of the CPU (e.g. 90%). > What recommendations can you guys suggest to take care of this issue ? I don't know what "this" issue is. Jim -- 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.