Couples of folks seem to work over performance tuning right now, so I thought bring that thread UP would give some cues
On Tue, Feb 19, 2013 at 12:02 PM, Richard Vézina < ml.richard.vez...@gmail.com> wrote: > Ok, find thanks for clarification. > > Richard > > > On Tue, Feb 19, 2013 at 11:30 AM, Niphlod <niph...@gmail.com> wrote: > >> No, it's not a parameter. >> He was just explaining that pool_size = 1 may be "weird to look at", and >> to think at it AS "recycle_connection=True". >> >> On Tuesday, February 19, 2013 5:16:29 PM UTC+1, Richard wrote: >> >>> Hello Michele, >>> >>> recycle_connection=True is a web2py connection string parameters? I >>> didn't see entry in the book, maybe it is not documented yet?! >>> >>> Richard >>> >>> >>> On Mon, Feb 18, 2013 at 5:50 PM, Michele Comitini <michele....@gmail.com >>> > wrote: >>> >>>> Niphold explanation is better than anything I could come out with. >>>> >>>> One could ask why pool_size=1 and not pool_size=0 then? >>>> A pool of one seems logical nonsense, but it works. >>>> 1 means that we keep recycling that same connection that is bound to >>>> the non-threading process. >>>> Think "recycle_connection=True" and write it as "pool_size=1" >>>> >>>> mic >>>> >>>> >>>> 2013/2/18 Richard Vézina <ml.richa...@gmail.com>: >>>> > Thanks Niphold for clarification, really appreciate. >>>> > >>>> > Richard >>>> > >>>> > >>>> > On Mon, Feb 18, 2013 at 4:17 PM, Niphlod <nip...@gmail.com> wrote: >>>> >> >>>> >> it "easy". if you run web2py using threads, then pooling is ok, >>>> since it's >>>> >> managed in a single process, recycling connections in a pool for >>>> each new >>>> >> thread that processes a request, and speeds up things a lot. >>>> >> >>>> >> A lot of webserver though use a single process to handle every >>>> request, >>>> >> using fork() (gunicorn, uwsgi, and so on....) to provide >>>> concurrency. It >>>> >> means that there are n processes able to serve up to n requests >>>> >> concurrently. >>>> >> In that case, there are no threads involved, so there's no need to >>>> use a >>>> >> pool, because every request is handled in a "freshly created" new >>>> single >>>> >> process. >>>> >> >>>> >> -- >>>> >> >>>> >> --- >>>> >> You received this message because you are subscribed to the Google >>>> Groups >>>> >> "web2py-users" group. >>>> >> To unsubscribe from this group and stop receiving emails from it, >>>> send an >>>> >> email to web2py+un...@googlegroups.com. >>>> >>>> >> For more options, visit https://groups.google.com/groups/opt_out. >>>> >> >>>> >> >>>> > >>>> > >>>> > -- >>>> > >>>> > --- >>>> > You received this message because you are subscribed to the Google >>>> Groups >>>> > "web2py-users" group. >>>> > To unsubscribe from this group and stop receiving emails from it, >>>> send an >>>> > email to web2py+un...@googlegroups.com. >>>> >>>> > For more options, visit https://groups.google.com/groups/opt_out. >>>> > >>>> > >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "web2py-users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to web2py+un...@googlegroups.com. >>>> >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>>> >>>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "web2py-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to web2py+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
