yes, this was always zero, mostly because it does not work with sqlite
(default db) and because when introduced we did not want to change the
previous behavior (backward compatibility).

On Jun 9, 6:59 pm, Doug Warren <doug.war...@gmail.com> wrote:
> Sorry to bump an old email, but was this changed at some point?
> (master) [dwar...@thebigwave gluon]$ grep pool_size\= *
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self,db,uri,pool_size=0,folder=None,db_codec 
> ='UTF-8'):
> dal.py:    def __init__(self, uri='sqlite://dummy.db', pool_size=0, 
> folder=None,
> sql.py:    def __init__(self, uri='sqlite://dummy.db', pool_size=0,
> sql.py:        pool_size=0,
>
> The default for every adapter type seems to be 0 not 10?
>
> On Tue, May 11, 2010 at 5:55 AM, Timothy Farrell <tfarr...@swgen.com> wrote:
> > When you create your model, there is a "pools" parameter that defaults to
> > 10.  This means that the one web2py process will use a pool of 10
> > connections on that one database.  It leaves the connections open even after
> > the request is served so that they can serve the next connection without
> > having to reconnect to the database.
>
> > -tim
>
> > On 5/11/2010 3:58 AM, vihang wrote:
>
> >> Hello,
>
> >> I am trying to understand the possible performance setback if I try to
> >> open multiple db connections. Is there some mechanism in web2py which
> >> would optimizes the number of open connections to the database?
>
> >> Vihang

Reply via email to