Re: Optimizing back-end: saving cycles or saving I/O (was: Re: [PATCH v2] Saving a few cycles, part 3/3)

On Wed, 2010-05-12 at 13:44 -0400, Hyrum K. Wright wrote:
> There may be other ways of caching this information, which would be great.

Maybe. Caches add complexity, and too many layers of caching (disk, OS,
application) can actually reduce performance in some scenarios.

I would suggest getting a better understanding of why this operation is
slow. Why is svn log opening each rev file ten times? Is this
intrinsically necessary? Going straight to optimizing the overused
low-level operations can provide a noticeable performance benefit, but
fixing the inefficient high-level algorithms is how you can turn minutes
into microseconds.
Received on 2010-05-12 21:13:31 CEST