From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Official Git mirror?
Date: Mon, 21 Feb 2011 22:33:23 +0200 [thread overview]
Message-ID: <8362sdt9f0.fsf@gnu.org> (raw)
In-Reply-To: <87zkppgoqy.fsf@wanadoo.es>
> From: Óscar Fuentes <ofv@wanadoo.es>
> Date: Mon, 21 Feb 2011 20:40:37 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> It seems that "nosmart" is used for compensating for servers with busy
> >> CPUs
> >
> > No, it's used to compensate for overly "smart" server when there's no
> > win in being smart, because you need to send everything anyway.
>
> But then the plan is failing, because the timings I posted show that
> "smart" wins over "nosmart" even when a weak server is servicing a
> mighty client over a fast network.
Sometimes it indeed makes no significant difference, but sometimes it
wins big time. Observe:
bzr://bzr.savannah.gnu.org/emacs/trunk
real 45m4.820s
user 15m58.380s
sys 0m12.910s
Transferred: 540480KiB (199.9K/s r:540403K w:77K)
bzr branch nosmart+bzr://bzr.savannah.gnu.org/emacs/trunk
real 16m30.189s
user 15m22.090s
sys 0m14.560s
Transferred: 780914KiB (789.2K/s r:780640K w:275K)
In the thread I mentioned on the Bazaar list, someone else also
reported a huge speedup:
> over a 3 Mbit/s connection:
>
> bzr://bzr.savannah.gnu.org/emacs/trunk
> 6949.356 Transferred: 469739kB (67.6kB/s r:469659kB w:80kB)
>
> nosmart+bzr://bzr.savannah.gnu.org/emacs/trunk
> 2919.117 Transferred: 524353kB (179.7kB/s r:524162kB w:191kB)
That's almost 2 hours slashed to 48 minutes, an almost 3-fold speedup.
> > The "smart" part is for sending less data, which is not going to win
> > for the initial checkout.
>
> You said on the other post that cloning time is network-bound. So being
> smart and sending less data would be better.
Not if "being smart" wastes CPU cycles on the server side and causes
it to use the available bandwidth less efficiently. See the network
throughput figures above, reported by bzr on .bzr.log.
next prev parent reply other threads:[~2011-02-21 20:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 21:11 Official Git mirror? Oleksandr Gavenko (aka gavenkoa)
2011-02-20 21:35 ` Eli Zaretskii
2011-02-20 21:59 ` Oleksandr Gavenko (aka gavenkoa)
2011-02-21 6:58 ` Eli Zaretskii
2011-02-21 23:29 ` Oleksandr Gavenko
2011-02-22 10:54 ` Eli Zaretskii
[not found] ` <mailman.8.1298372068.26362.help-gnu-emacs@gnu.org>
2011-02-24 19:31 ` Vagn Johansen
2011-02-24 19:55 ` Eli Zaretskii
2011-02-21 5:36 ` Óscar Fuentes
2011-02-21 6:58 ` Leo
2011-02-21 7:58 ` Eli Zaretskii
2011-02-21 16:09 ` Óscar Fuentes
2011-02-21 18:56 ` Eli Zaretskii
2011-02-21 20:08 ` Óscar Fuentes
[not found] ` <mailman.11.1298266625.16274.help-gnu-emacs@gnu.org>
2011-02-21 8:52 ` Tim X
2011-02-21 14:31 ` Official Git mirror? -- Request Perry Smith
2011-02-21 14:57 ` andrea crotti
2011-02-21 18:17 ` Official Git mirror? Óscar Fuentes
2011-02-21 19:02 ` Eli Zaretskii
2011-02-21 19:40 ` Óscar Fuentes
2011-02-21 20:33 ` Eli Zaretskii [this message]
2011-02-21 20:57 ` Óscar Fuentes
2011-02-21 21:15 ` Eli Zaretskii
[not found] ` <mailman.11.1298320422.21303.help-gnu-emacs@gnu.org>
2011-02-23 9:16 ` Giorgos Keramidas
2011-02-23 12:32 ` Eli Zaretskii
2011-02-23 19:38 ` jun yu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8362sdt9f0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).