William Stein wrote: > On Fri, Sep 11, 2009 at 10:13 PM, Pat LeSmithe <qed...@gmail.com> wrote: >> Assuming the code >> http://trac-hacks.org/svn/ticketbacklinksmacro/0.11/TicketBackLinksDescription/macro.py >> actually works, I think we can tailor the SQL query to select records >> from the "ticket" table. >> >> I don't know how this affects performance. Perhaps the usual queries >> account for Sage trac's slow behavior. What is the current backend >> database? Is there a faster alternative? > Is trac slow?? It used to be slow/unstable maybe 2 months ago, so Mike > Hansen changed the backend to use MySQL, and then it became much faster and > far more stable (0 crashes since).
Sometimes, ticket pages "stall" for several seconds upon being opened in a Firefox tab, as if the browser were still waiting for a response from the server. But my experience may not be representative, and other factors, such as network congestion, may well be the source. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
