On Sep 30, 3:37 pm, Michael Bayer <[EMAIL PROTECTED]> wrote:
> > Makes sense and now i clearly see the pattern of 2 connections per
> > thread. Thanks for clearing that up.
>
> per process. big difference :).
Err yes, per process. Matching up to the numbers defined in Min/Max
spare servers.
--
>
> Makes sense and now i clearly see the pattern of 2 connections per
> thread. Thanks for clearing that up.
per process. big difference :).
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
On Sep 30, 10:35 am, Michael Bayer <[EMAIL PROTECTED]> wrote:
> On Sep 30, 10:31 am, Wayne Witzel <[EMAIL PROTECTED]> wrote:
>
>
>
> > Is connection pooling with SQLAlchemy under Pylons supported when
> > running under mod_wsgi? Is there some special magic to get it working?
>
> > I have the follo
On Sep 30, 10:31 am, Wayne Witzel <[EMAIL PROTECTED]> wrote:
> Is connection pooling with SQLAlchemy under Pylons supported when
> running under mod_wsgi? Is there some special magic to get it working?
>
> I have the following INI settings.
>
> sqlalchemy.default.pool_size = 1
> sqlalchemy.diary
Is connection pooling with SQLAlchemy under Pylons supported when
running under mod_wsgi? Is there some special magic to get it working?
I have the following INI settings.
sqlalchemy.default.pool_size = 1
sqlalchemy.diary.pool_size = 1
sqlalchemy.default.max_overflow = 0
sqlalchemy.diary.max_ov
