From: Tom Lord <lord@emf.net>
To: torvalds@osdl.org
Cc: git@vger.kernel.org
Subject: Re: on when to checksum
Date: Wed, 20 Apr 2005 15:52:33 -0700 (PDT) [thread overview]
Message-ID: <200504202252.PAA16837@emf.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0504201539180.6467@ppc970.osdl.org> (message from Linus Torvalds on Wed, 20 Apr 2005 15:41:47 -0700 (PDT))
From: Linus Torvalds <torvalds@osdl.org>
On Wed, 20 Apr 2005, Tom Lord wrote:
>
> I think you have made a mistake by moving the sha1 checksum from the
> zipped form to the inflated form. Here is why:
I'd have agreed with you (and I did, violently) if it wasn't for the
performance issues. It makes a huge difference for write-tree, and to me,
clearly performance _does_ matter.
Fractions of seconds may not sound like a lot, but they add up. I work
with 200-patch series myself all the time, so I'm very sensitive to a 0.3
second difference in performance.
How many times per day do you invoke `write-tree' and why?
It takes a large multiple of `0.3s' to get me to take you seriously
on this point.
I have long harbored the suspician that your perceived bandwidth
implies that you process a lot of patches unread or barely read --
implying that your day-to-day bitslingling could/should largely be
handled by an Arch-style patch-queue-manager (a script).
-t
next prev parent reply other threads:[~2005-04-20 22:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 22:25 on when to checksum Tom Lord
2005-04-20 22:41 ` Linus Torvalds
2005-04-20 22:52 ` Tom Lord [this message]
2005-04-20 23:07 ` Linus Torvalds
2005-04-20 23:39 ` Tom Lord
2005-05-02 19:21 ` Tom Lord
2005-05-02 19:57 ` Linus Torvalds
2005-04-21 16:53 ` Andrew Timberlake-Newell
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=200504202252.PAA16837@emf.net \
--to=lord@emf.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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 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.