From: "Lukas Sandström" <lukass@etek.chalmers.se>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <junkio@cox.net>,
"Alex Riesen" <raa.lkml@gmail.com>,
"Lukas Sandström" <lukass@etek.chalmers.se>
Subject: Re: [PATCH] speedup allocation in pack-redundant.c
Date: Tue, 22 Nov 2005 23:48:51 +0100 [thread overview]
Message-ID: <4383A053.8020100@etek.chalmers.se> (raw)
In-Reply-To: <7vek58ct4b.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Alex Riesen <raa.lkml@gmail.com> writes:
>
>
>>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)
Did someone else notice an improvement?
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.
/Lukas
next prev parent reply other threads:[~2005-11-22 22:48 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 [this message]
2005-11-22 23:08 ` Junio C Hamano
2005-11-22 23:46 ` Alex Riesen
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=4383A053.8020100@etek.chalmers.se \
--to=lukass@etek.chalmers.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@gmail.com \
/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.