[darcs-devel] [issue1678] performance regression in check/whatsnew/record (2.3.x)

[Petr Ročkai]

Petr Ročkai <me at mornfall.net> added the comment:

> === darcs ===
>
>                 ||  darcs-2.2.1        | darcs-2.3.1       |  darcs
> ================++=====================+===================+===============
>           check ||        11.7s 183.0M |       11.0s 55.0M |  42.4s 258.0M
>          repair ||        11.8s 183.0M |       11.1s 55.0M |  44.2s 272.0M
>
>
> === ghc-hashed ===
>
>                 ||  darcs-2.2.1         | darcs-2.3.1        |   darcs
> ================++======================+====================+===============
>           check ||       172.3s 1210.0M |      160.5s 146.0M |       -      -
>          repair ||       173.0s 1287.0M |      127.7s 146.0M | 1190.6s 355.0M
>
> For details, see
>  - http://lists.osuosl.org/pipermail/darcs-users/2010-January/022832.html
>  - http://lists.osuosl.org/pipermail/darcs-users/2010-January/022833.html
I have fixed the worst part of this problem in hashed-storage. Currently
only available in its darcs version.

On my machine: darcs-2.3 = 1:53, darcs-HEAD = 2:49 (on ghc-hashed).

That's still a substantial difference, but much less than 2:06 against
almost 20 minutes. I don't think I will have the time to bring this
further down in time for darcs 2.4, so we'll have to accept this as a
price for the refactoring. (The primary cause for this was my crusade to
remove SlurpDirectory which is not yet complete, but it is reasonably
close to completion, so maybe in 2.5 we can get rid of that...)

Yours,
   Petr.

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue1678>
__________________________________