All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Turner <dturner@twopensource.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Duy Nguyen <pclouds@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Junio C Hamano <gitster@pobox.com>,
	Michael Haggerty <mhagger@alum.mit.edu>,
	David Turner <dturner@twitter.com>
Subject: Re: [PATCH v6 2/2] refs.c: SSE4.2 optimizations for check_refname_component
Date: Thu, 05 Jun 2014 15:26:02 -0400	[thread overview]
Message-ID: <1401996362.18134.179.camel@stross> (raw)
In-Reply-To: <539062D9.60000@web.de>

On Thu, 2014-06-05 at 14:30 +0200, Torsten Bögershausen wrote:
> On 2014-06-04 23.16, David Turner wrote:
> > 
> > Sure!  I actually went with > 120k to make measurement easier:
> > https://github.com/dturner-tw/many-refs
> Hm, I didn't get so man
> 
> git remote -v
> origin  https://github.com/dturner-tw/many-refs 
> 
>  wc .git/packed-refs 
>      750    1130   38868 .git/packed-refs
> 

Oops.  It looks like I forgot to push all of the refs.  And when I try,
it fails with "fatal: cannot exec 'send-pack': Argument list too long"

I hacked git to send batches of 1000; maybe I'll actually make a real
patch with ARG_MAX at some point. Anyway, this is uploading now, but I
estimate that it will take at least five hours, because github is being
really slow about this.

...
> where only patch 1/2 doesn't seem to speed up things on my system:
...

I would not expect a noticeable change on a tiny number of refs; it's
only when ref parsing takes up a large percentage of runtime -- tens of
thousands of refs.

  parent reply	other threads:[~2014-06-05 19:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-04  3:38 [PATCH v6 1/2] refs.c: optimize check_refname_component() David Turner
2014-06-04  3:38 ` [PATCH v6 2/2] refs.c: SSE4.2 optimizations for check_refname_component David Turner
2014-06-04  8:04   ` Torsten Bögershausen
2014-06-04 11:21     ` Duy Nguyen
2014-06-04 14:25       ` Torsten Bögershausen
2014-06-04 21:16         ` David Turner
2014-06-05 12:30           ` Torsten Bögershausen
2014-06-05 12:58             ` Ondřej Bílka
2014-06-05 19:26             ` David Turner [this message]
2014-06-05 21:42               ` Torsten Bögershausen
2014-06-05 22:02                 ` David Turner
2014-06-04 21:14     ` David Turner
2014-06-04 21:46       ` Junio C Hamano
2014-06-05 19:27         ` David Turner

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=1401996362.18134.179.camel@stross \
    --to=dturner@twopensource.com \
    --cc=dturner@twitter.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=mhagger@alum.mit.edu \
    --cc=pclouds@gmail.com \
    --cc=tboegi@web.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.