On Wed, Dec 31, 2008 at 09:29:22AM -0500, Nathan Gray wrote:
> Much better results than 2.1.2 and 2.2.0pre1.
> 
> Now I just need to compare these with darcs 1.0.9.

I have run darcs-benchmark using darcs 1.0.9 and am now able to
compare:

  darcs 1.0.9 on version 1 repository
  darcs 2.2.pre2 on version 1 repository
  darcs 2.2.pre2 on version 2 repository

On the (rather large) cap repository, darcs22pre2 used about a third
more memory and took more than three times as long to get.

For some reason the check and repair benchmarks failed for darcs109,
but darcs22pre2 took more time and used more memory for these on the
version 2 repository than on the version 1 repository.  Likewise for
repair.

Pulls are somewhat similar when using a version 1 repository, but use
more than six times as much memory and take about twice as long on the
version 2 repository.

=== big-zoo/cap ===

          || darcs109     | darcs202      | darcs210      | darcs22pre2     
==========++==============+===============+===============+=================
 get full ||    59.0s 21M |   496.6s 259M |   483.2s 259M |      455.8s 259M
 get lazy ||        -   - |   475.8s 259M |   472.0s 259M |      454.5s 259M
    check ||        -   - |   467.9s 259M |   501.4s 259M |      779.9s 285M
   repair ||        -   - |        -    - |        -    - |      806.8s 285M
 pull 100 ||   246.7s 22M |   372.5s  20M |   276.5s  20M |      332.6s  23M
pull 1000 ||   453.2s 41M |   440.2s  45M |   363.1s  37M |      418.5s  45M

=== big-zoo/cap2 ===

          || darcs22pre2     
==========++=================
 get full ||      199.7s  29M
 get lazy ||       68.4s   2M
    check ||     1335.6s 312M
   repair ||     1243.0s 312M
 pull 100 ||      411.0s 177M
pull 1000 ||     1016.6s 272M

On the (somewhat smaller) systems repository, getting used less than a
tenth as much memory on the version 2 repository, but took five times
as long.

It took less time to check and to repair using darcs22pre2, but used
two to three times as much memory as darcs109.

Pulling fewer patches on darcs109 was faster, but pulling more patches
was faster using darcs22pre2.  Memory usage was similar for all of
the 'pull' benchmarks.

=== big-zoo/systems ===

          || darcs109      | darcs202      | darcs210      | darcs22pre2     
==========++===============+===============+===============+=================
 get full ||     6.2s  11M |    13.7s  79M |    11.7s  80M |       11.6s  79M
 get lazy ||        -    - |    12.0s  79M |    11.1s  79M |       10.4s  79M
    check ||    21.1s  38M |    12.6s  79M |    10.0s  79M |        8.6s 106M
   repair ||    20.7s  47M |   122.0s 218M |   147.7s 218M |        9.8s 115M
 pull 100 ||    57.5s 280M |    98.0s 277M |    86.9s 277M |       96.0s 277M
pull 1000 ||   182.4s 329M |   165.1s 347M |   152.3s 346M |      145.8s 347M

=== big-zoo/systems2 ===

          || darcs22pre2     
==========++=================
 get full ||       51.1s   1M
 get lazy ||       17.8s   0M
    check ||       14.3s 107M
   repair ||       14.5s 107M
 pull 100 ||       83.2s 274M
pull 1000 ||      114.5s 319M

I am encouraged that darcs22pre2 on a version 2 repository is
performing so much better than earlier versions of darcs2.  I am still
concerned that it uses so much more memory for check and repair, and
sometimes pull, and that it is so much slower for pulls and gets.

-kolibrie

_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users

Reply via email to