From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Teach Git how to parse standard power of 2 suffixes.
Date: Sun, 31 Dec 2006 00:47:41 -0500 [thread overview]
Message-ID: <20061231054741.GA6106@spearce.org> (raw)
In-Reply-To: <7vejqgk4l1.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano <junkio@cox.net> wrote:
> Shawn Pearce <spearce@spearce.org> writes:
>
> > So in your test case where you thought you entered 20 pages, what you
> > really had was just 2 pages. We rounded 20 bytes down to 0 pages,
> > then forced that to a minimum of 2 pages. :-)
>
> Yes.
>
> And I found something else that is interesting. I still had 2
> pages windows but reduced packedgitlimit to 256kB and re-run the
> same test to reproduce all merges in git.git. It still did not
> fail, but it took even shorter wallclock time (again, it is only
> 3 seconds or so out of 5 1/2 minuts, so it is probably
> statistically insignificant).
Its possible the packed_git.windows list is hurting us here.
Its O(n) to locate a given window. The larger the ratio between
packedGitWindowSize and packedGitLimit the longer that list can get,
and the longer it can take to locate a window.
Maybe that should be a simple red-black tree?
More testing probably needs to be done though.
--
Shawn.
next prev parent reply other threads:[~2006-12-31 5:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 2:02 [PATCH 1/2] Teach Git how to parse standard power of 2 suffixes Shawn O. Pearce
2006-12-31 2:33 ` Junio C Hamano
2006-12-31 2:38 ` Shawn Pearce
2006-12-31 2:57 ` Junio C Hamano
2006-12-31 3:01 ` Shawn Pearce
2006-12-31 5:38 ` Junio C Hamano
2006-12-31 5:47 ` Shawn O. Pearce [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-31 3:13 Shawn O. Pearce
2006-12-31 5:56 ` Junio C Hamano
2006-12-31 6:12 ` Shawn O. Pearce
2006-12-31 6:23 ` Junio C Hamano
2006-12-31 6:26 ` Shawn O. Pearce
2006-12-31 6:30 ` Junio C Hamano
2006-12-31 6:36 ` Shawn O. Pearce
2006-12-31 6:48 ` Shawn O. Pearce
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=20061231054741.GA6106@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).