-On [20080220 09:54], Christian Boos ([EMAIL PROTECTED]) wrote: >I'm a bit short on time these days, so I can't really say /when/ I'll be >able to sit down again and try to fix the issue with Genshi. On the Trac >side, it's quite clear what has to be done (looking at >http://trac.edgewall.org/ticket/6614#comment:18): > > 1. do an explicit garbage collection after each request >(http://trac.edgewall.org/attachment/ticket/6614/explicit_gc.diff) > 2. tune the pool usage in the svn backend: > a. for the _history call >(http://trac.edgewall.org/attachment/ticket/6614/fix-_history.diff) > b. for listing long directories (#5782) > > >I can commit 1. and 2.a. shortly, and with that (plus using Python 2.5 >on the server), things will start to look quite acceptable.
By all means. :) >2.b. needs more work, but is not a blocker, I think, so it could well >wait 0.11.1 (or 0.12 if I end up reworking the Pool code entirely). > >Now, if for any reason the server hits the problem with Genshi >(http://trac.edgewall.org/ticket/6614#comment:40), the memory usage will >increase dramatically again. To fix that one, I think the approach >outlined in the last paragraph of >http://trac.edgewall.org/ticket/6614#comment:38 will work, I only need >some more time (or someone else to do it, of course). Well, I started yesterday looking at the remaining tickets for 0.11 in order to close them, but it seems you went through half of it after Odd Simon and me closed one. :) I'll check the tickets full history when I get home. >> I mean, might it make sense to release 0.11.0 now to get the release out the >> door and continue to look for these more elusive cases for a 0.11.1 release? > >Well, it's a more a matter of fixing the Genshi issue for 0.5, then make >Trac 0.11 depend on that version. As I said in the comment:38 (linked >above), 0.4.x has the #G158 bug which makes Trac unreliable in >multithreaded setup, so I wouldn't recommend using it. Ok, but then releasing Genshi 0.5 becomes a blocking priority before releasing Trac 0.11, since we need to get the eggs, especially for Windows with speedups, out there. >> I am just trying to get a sense of the choice between finally releasing 0.11 >> and stability for the end-users. > >Perhaps we can make another beta after the two patches on #6614 (listed >in 1. and 2.a above) are committed, and see how things work in practice? Sure, I think our encountered issues warrant another beta regardless. -- Jeroen Ruigrok van der Werven <asmodai(-at-)in-nomine.org> / asmodai イェルーン ラウフロック ヴァン デル ウェルヴェン http://www.in-nomine.org/ | http://www.rangaku.org/ There is time in life for everything... --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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-dev?hl=en -~----------~----~----~----~------~----~------~--~---
