From: "Marco Costalba" <mcostalba@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH WIP] sha1-lookup: make selection of 'middle' less aggressive
Date: Tue, 1 Jan 2008 00:47:47 +0100 [thread overview]
Message-ID: <e5bfff550712311547x484757f8lc3c8456a2719e827@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.00.0712311232520.32517@woody.linux-foundation.org>
On Dec 31, 2007 9:37 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
>
> Even today, I don't really know of a better compression choice, despite
> now being more aware of how critical uncompression performance is.
>
In the kernel, from not long ago, is used also LZO compression that
_seems_ much faster to decompress then zlib
http://lkml.org/lkml/2007/5/1/297
The developer, Richard Purdie, says it's also 40% faster to read for jffs2.
>
> Quite possibly, the cache miss costs dominate over any algorithmic costs.
>
What way could be used to build up a test to check this?
Thanks
Marco
next prev parent reply other threads:[~2007-12-31 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-30 10:22 [PATCH WIP] sha1-lookup: more memory efficient search in sorted list of SHA-1 Junio C Hamano
2007-12-30 11:38 ` [PATCH WIP] sha1-lookup: make selection of 'middle' less aggressive Junio C Hamano
2007-12-30 19:06 ` Marco Costalba
2007-12-30 19:12 ` Marco Costalba
2007-12-31 22:40 ` Shawn O. Pearce
2007-12-30 19:58 ` Linus Torvalds
2007-12-30 21:49 ` Junio C Hamano
2007-12-30 22:04 ` Marco Costalba
2007-12-31 20:37 ` Linus Torvalds
2007-12-31 23:47 ` Marco Costalba [this message]
2008-01-01 6:36 ` Jeff King
2008-01-01 8:40 ` Marco Costalba
2008-01-01 9:01 ` Marco Costalba
2008-01-01 14:51 ` Pierre Habouzit
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=e5bfff550712311547x484757f8lc3c8456a2719e827@mail.gmail.com \
--to=mcostalba@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=torvalds@linux-foundation.org \
/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).