-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Not long back I switched from the prefork apache MPM to the worker one, at the suggestion of coderanger (due to better memory efficiency etc). I set it up to run on two processes each spawning a number of threads.
Yesterday we encountered Trac being unable to connect to the database (Postgres 8.2, Trac 0.11 RC2), and when investigating it noticed that trac only had two connections open (two large requests were being processed at this time leading to the site being unavailable to other requests). I asked about this in IRC and was told that there were issues with the pooling in RC2 and that I should upgrade to 0.11. coderanger also mentioned the TRAC_DB_POOL_SIZE environment variable which could be used to control the connection pooling. I did that, but Trac still only held two connections open. I viewed trac/db/pool.py and saw no mention of TRAC_DB_POOL_SIZE. Looking at the file on trunk (of t.e.o) I do see it there, which suggests that TRAC_DB_POOL_SIZE was actually added post 0.11. I also don't see it in that file on the 0.11-stable branch. Is there any estimate as to when this change might be released (e.g. 0.11.1)? Thanks. - -- Russ. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIY+eWhXYlbEtYt2wRAoByAKDC5gaiy/mf1hczm16w3GrRgCFcdgCeJ6ZW 9tcJJCLJ2XbF+gn3yQKEmvQ= =OPxK -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
