From: Siddharth Agarwal <sid0@fb.com>
To: Jeff King <peff@peff.net>, <git@vger.kernel.org>
Cc: Ben Maurer <bmaurer@fb.com>
Subject: Re: [PATCH/RFC 0/6] reuse deltas found by bitmaps
Date: Wed, 26 Mar 2014 15:40:47 -0700 [thread overview]
Message-ID: <5333576F.1050603@fb.com> (raw)
In-Reply-To: <20140326072215.GA31739@sigill.intra.peff.net>
On 03/26/2014 12:22 AM, Jeff King wrote:
> [tl;dr the patch is the same as before, but there is a script to measure
> its effects; please try it out on your repos]
Here are results from one of our repos:
Test origin HEAD
-------------------------------------------------------------------------
5311.3: server (1 days) 1.77(2.49+0.15) 0.76(0.65+0.12) -57.1%
5311.4: size (1 days) 7.8M 3.1M -60.2%
5311.5: client (1 days) 0.56(0.48+0.03) 1.18(0.97+0.05) +110.7%
5311.7: server (2 days) 2.79(3.68+0.25) 0.77(0.65+0.14) -72.4%
5311.8: size (2 days) 24.2M 6.8M -71.8%
5311.9: client (2 days) 1.14(0.95+0.10) 2.72(2.33+0.13) +138.6%
5311.11: server (4 days) 3.70(4.76+0.28) 0.84(0.72+0.14) -77.3%
5311.12: size (4 days) 51.2M 18.9M -63.0%
5311.13: client (4 days) 2.29(2.02+0.29) 4.58(3.91+0.30) +100.0%
5311.15: server (8 days) 5.16(7.48+0.38) 1.20(1.18+0.21) -76.7%
5311.16: size (8 days) 78.3M 42.6M -45.5%
5311.17: client (8 days) 3.73(3.67+0.40) 6.59(5.95+0.51) +76.7%
5311.19: server (16 days) 6.48(10.27+0.52) 1.60(1.85+0.27) -75.3%
5311.20: size (16 days) 97.5M 64.0M -34.4%
5311.21: client (16 days) 5.31(5.76+0.57) 8.99(8.61+0.68) +69.3%
5311.23: server (32 days) 8.56(14.00+0.67) 2.31(2.91+0.37) -73.0%
5311.24: size (32 days) 124.7M 92.0M -26.2%
5311.25: client (32 days) 7.69(9.20+0.76) 12.80(13.07+0.91) +66.4%
5311.27: server (64 days) 37.47(45.48+1.55) 29.75(29.58+0.96) -20.6%
5311.28: size (64 days) 245.5M 207.1M -15.6%
5311.29: client (64 days) 15.11(18.26+1.58) 25.02(25.90+2.03) +65.6%
5311.31: server (128 days) 43.85(57.02+2.57) 29.88(29.54+1.35) -31.9%
5311.32: size (128 days) 507.3M 461.6M -9.0%
5311.33: client (128 days) 27.13(31.54+3.32) 37.76(39.49+3.16) +39.2%
I'm currently running tests on a much larger repo than that. The full
perf run will take several hours on that, so the soonest I can likely
publish results for that is tomorrow.
next prev parent reply other threads:[~2014-03-26 22:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 7:22 [PATCH/RFC 0/6] reuse deltas found by bitmaps Jeff King
2014-03-26 7:22 ` [PATCH 1/6] t/perf-lib: factor boilerplate out of test_perf Jeff King
2014-03-26 22:34 ` Junio C Hamano
2014-03-26 7:22 ` [PATCH 2/6] t/perf/aggregate: factor our percent calculations Jeff King
2014-03-26 7:22 ` [PATCH 3/6] t/perf: add infrastructure for measuring sizes Jeff King
2014-03-26 7:22 ` [PATCH 4/6] t/perf: add perf tests for fetches from a bitmapped server Jeff King
2014-03-26 7:23 ` [PATCH 5/6] pack-bitmap: save "have" bitmap from walk Jeff King
2014-03-26 7:23 ` [PATCH 6/6] pack-objects: reuse deltas for thin "have" objects Jeff King
2014-03-28 4:23 ` Eric Sunshine
2014-03-26 17:33 ` [PATCH/RFC 0/6] reuse deltas found by bitmaps Junio C Hamano
2014-03-26 18:13 ` Jeff King
2014-03-26 22:31 ` Junio C Hamano
2014-03-26 22:36 ` Jeff King
2014-03-27 1:13 ` Jeff King
2014-03-27 16:36 ` Junio C Hamano
2014-03-26 22:40 ` Siddharth Agarwal [this message]
2014-03-27 14:09 ` Siddharth Agarwal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5333576F.1050603@fb.com \
--to=sid0@fb.com \
--cc=bmaurer@fb.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).