From: "Shawn O. Pearce" <spearce@spearce.org>
To: Sam Vilain <sam@vilain.net>
Cc: Srijak Rijal <srijak@gmail.com>, git@vger.kernel.org
Subject: Re: Gittorent .. avahi ?
Date: Tue, 3 Apr 2007 01:31:45 -0400 [thread overview]
Message-ID: <20070403053145.GF15922@spearce.org> (raw)
In-Reply-To: <46106AD3.6000204@vilain.net>
Sam Vilain <sam@vilain.net> wrote:
...
> I think in BitTorrent there is an *over*-emphasis on making the tracker
> load light, because people want to be able to run them on the most
> dirt-cheap hosting account they can find, because they might get shut
> down and don't want a huge outlay. But with GitTorrent, a large number
> of the tracker providers are going to be software houses, and people
> already running mirroring services - and so the increased load will be
> more than justified by the reduced overall load.
...
Yes, I agree entirely. Almost anyone who is going to be running a
tracker for GitTorrent would already today be running the anonymous
Git daemon. These users (ahm... kernel.org) would like to reduce
load on their servers if clients can get the data from elsewhere.
Hosting a tracker is still load, but should be a *much* lower load.
Note that kernel.org's entire load appears to be disk IO (as stated
by hpa on many occasions). A little bit of extra CPU and network
bandwidth (for tracker maintenance) to cut disk IO in half (due to
less object directory accesses) would probably be major improvement
for them, and would still cut their overall network bandwidth as
clients would get packs from other nodes in the P2P system.
> Anyway, the old warning about scope creep applies to this idea - working
> from the bottom up is a lot better for getting things done than thinking
> big. Just look at me, I think big all the time and never get anything
> done ;-) There will be a lot of interesting technologies enabled by
> gittorrent.
I agree. The biggest risk to any GSoC project is not the student,
or the community, or the technology... but its scope creep.
Of course this is true of *any* project.
Git evolved. Linux evolved. Apache evolved. None of them set
out on day one with a huge list of "must have" features that they
coded from scratch. Every one of those projects organically grew
as new features were desired and old bugs fixed.[*1*]
[*1*] Yes, I know, Linus did set out when writing both Linux and
Git to create something that did X... but X was a pretty
small concept. Git started as a "track Linus' state thing",
not as a full SCM. ;-)
--
Shawn.
next prev parent reply other threads:[~2007-04-03 5:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-01 17:59 Gittorent .. avahi ? Srijak Rijal
2007-04-02 2:30 ` Sam Vilain
2007-04-03 5:31 ` Shawn O. Pearce [this message]
2007-04-03 18:25 ` Jonas Fonseca
2007-04-03 19:44 ` Srijak Rijal
2007-04-04 0:30 ` Jakub Narebski
2007-04-04 0:58 ` Srijak Rijal
2007-04-04 7:57 ` Jakub Narebski
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=20070403053145.GF15922@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
--cc=srijak@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 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).