I thought I should follow up on this ticket.

I've implemented something fairly similar to the Alec's Advanced Search
suggestion - each component listens to its own ChangeListeners and indexes
the documents at that time. I've only implemented the wiki and ticket
systems so far, but that's because I just recently became comfortable with
the approach I'm using.

Right now it (re)creates the full index when you run "trac-admin env
upgrade," or duing the intial setup. I'm doing my testing on a copy of a
real internal trac install of ~600 wiki page; 1700 ticket. I indexed a on a
vmware workstation running on my desktop in about 4 minutes, but I haven't
considered performance at all yet and it was CPU limited. The index is 5.1MB
(sqlite db is 69MB), so disk space is basically not an issue. I think by
using straight SQL for that, instead of moving around Ticket and Wiki
objects will yield significantly superior performance. I haven't noticed a
change in commit times when changing pages/tickets.

On Thu, Mar 12, 2009 at 12:24 PM, Chris Mulligan
<[email protected]>wrote:

> Yeah, I have big concerns about not making this complicated for use in
> production. That's a big reason I was excited about Whoosh, it's pure python
> like Pygments vs Enscript/Silvercity.
>
> The multiprocessing module might be a big win, but I can't imagine you are
> ready to set the minimum version at 2.6. I'll experiment with threading &
> queues to see how that handles things. The number of different ways trac can
> be used in production (wsgi, cgi, fastcgi, mod_python, tracd, I'm sure I'm
> forgetting some) certainly makes it a more "fun" problem.

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to