[Trac-dev] Re: Improving next_rev for scoped svn paths

> Was he using a recent enough 0.11dev? In particular, was this happening
> despite of r6594?

Yes, even on trunk.  The memory usage remains "reasonable",  it just takes
a long time to read the revs from the disk (especially over nfs).  The
timings I gave were for a local reposory, requesting ~r7000 out of 13000
total, where no further change exists at that path.  Here's an example on
t.e.o.:

http://trac.edgewall.org/changeset/2826 -> averages 2s
http://trac.edgewall.org/changeset/2826/sandbox/trac-xref -> averages 18s

Tim

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Development" group.
To post to this group, send email to trac-dev <at> googlegroups.com
To unsubscribe from this group, send email to trac-dev-unsubscribe <at> googlegroups.com
For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---