From: Alex Riesen <raa.lkml@gmail.com>
To: "Lukas Sandström" <lukass@etek.chalmers.se>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] speedup allocation in pack-redundant.c
Date: Wed, 23 Nov 2005 00:46:22 +0100 [thread overview]
Message-ID: <20051122234622.GD2916@steel.home> (raw)
In-Reply-To: <4383A053.8020100@etek.chalmers.se>
Lukas Sandström, Tue, Nov 22, 2005 23:48:51 +0100:
> >>Subject: [PATCH] speedup allocation in pack-redundant.c
> >>Reuse discarded nodes of llists
> >>Signed-off-by: Alex Riesen <ariesen@harmanbecker.com>
> >
> > I think making allocation/deallocation to the central place is a
> > good cleanup, but I am not sure about the free-nodes reusing.
> > Does this make difference in real life? If so, it might be
> > worth doing the slab-like allocation, since free-nodes are very
> > small structure and malloc overhead is not ignorable there.
> >
> I have done some tests, and unfortunatley I saw approx. zero
> improvement with Alex's patch. (less than 10ms difference when
> total runtime is 1.850s, tested on http://home.arcor.de/fork0/download/idx.tar.gz)
Can I suggest you try it in a really really weird environment? Like
Cygwin. And switch some virus scanner on.
> Did someone else notice an improvement?
My test case had over 100k files in it (just don't ask why. Weird
environments, weird projects, ...)
> It's a nice idea though. I'll look into doing slab-allocation
> for the fun of it, but I'm not really sure that malloc is the
> bottleneck.
Yes, it usually is not a bottleneck. I think, it just another
exception.
next prev parent reply other threads:[~2005-11-22 23:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 14:56 [PATCH] speedup allocation in pack-redundant.c Alex Riesen
2005-11-22 20:41 ` Junio C Hamano
2005-11-22 22:48 ` Lukas Sandström
2005-11-22 23:08 ` Junio C Hamano
2005-11-22 23:46 ` Alex Riesen [this message]
2005-11-22 23:00 ` Alex Riesen
2005-11-22 23:14 ` Lukas Sandström
2005-11-22 23:38 ` Alex Riesen
2005-11-22 23:55 ` Lukas Sandström
2005-11-23 7:31 ` Alex Riesen
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=20051122234622.GD2916@steel.home \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=lukass@etek.chalmers.se \
/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).