#2176: Trac database connections should be pooled
--------------------+------------------
Reporter: strk | Owner: strk
Type: task | Status: new
Priority: normal | Milestone:
Component: Trac | Keywords:
--------------------+------------------
Right after starting PostgreSQL 200 connections get filled by Trac. We
want to use some database pooling instead.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2176>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2176: Trac database connections should be pooled
--------------------+-------------------
Reporter: strk | Owner: strk
Type: task | Status: new
Priority: normal | Milestone:
Component: Trac | Resolution:
Keywords: |
--------------------+-------------------
Comment (by strk):
https://trac.edgewall.org/ticket/4347 may be related.
Right now I see 21 "idle" connections to the "trac_postgis" database and
124 idle connections in total to trac_X databases
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2176#comment:1>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2176: Trac database connections should be pooled
--------------------+-------------------
Reporter: strk | Owner: strk
Type: task | Status: new
Priority: normal | Milestone:
Component: Trac | Resolution:
Keywords: |
--------------------+-------------------
Comment (by strk):
We could experiment with TRAC_DB_POOL_SIZE env variable (not sure how to
set in /etc/apache2/includes/trac_env.inc)
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2176#comment:2>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2176: Trac database connections should be pooled
--------------------+-------------------
Reporter: strk | Owner: strk
Type: task | Status: new
Priority: normal | Milestone:
Component: Trac | Resolution:
Keywords: |
--------------------+-------------------
Comment (by strk):
was the limit in number of apache processes recently lifted btw ? By
TemporSent if I'm not mistaken ? As that'd probably increase the number of
connections too (pooling is per-process)
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2176#comment:3>
OSGeo <https://osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2176: Trac database connections should be pooled
---------------------------+------------------------
Reporter: strk | Owner: strk
Type: task | Status: closed
Priority: normal | Milestone:
Component: SysAdmin/Trac | Resolution: duplicate
Keywords: |
---------------------------+------------------------
Changes (by robe):
* status: new => closed
* resolution: => duplicate
Comment:
This is a dupe of #3246
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2176#comment:4>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#2176: Trac database connections should be pooled
---------------------------+-----------------------
Reporter: strk | Owner: strk
Type: task | Status: reopened
Priority: normal | Milestone:
Component: SysAdmin/Trac | Resolution:
Keywords: |
---------------------------+-----------------------
Changes (by strk):
* resolution: duplicate =>
* status: closed => reopened
Comment:
I don't think this is a duplicate, trac itself supports pooling and does
in fact pool connections, BUT apache starts up to 100 processes (150 by
default) and each of them will use its own pool, resulting in an exploding
number of connections to the database.
I agree pgbouncer could be one possible solution, but reducing number of
apache processes might be another (mod_wsgi ?)
--
Ticket URL: <#2176 (Trac database connections should be pooled) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.