Update timing info to add another set of data points.

This commit is contained in:
Brett Cannon 2009-02-22 22:42:44 +00:00
parent dfcfb32da3
commit 9664660ff4
1 changed files with 16 additions and 13 deletions

View File

@ -203,7 +203,7 @@ Contenders
========== ========== ======= =================================== ========================================== ========== ========== ======= =================================== ==========================================
Name Short Name Version 2.x Trunk Mirror 3.x Trunk Mirror Name Short Name Version 2.x Trunk Mirror 3.x Trunk Mirror
---------- ---------- ------- ----------------------------------- ------------------------------------------ ---------- ---------- ------- ----------------------------------- ------------------------------------------
Bazaar_ bzr 1.11 http://code.python.org/python/trunk http://code.python.org/python/3.0 Bazaar_ bzr 1.12 http://code.python.org/python/trunk http://code.python.org/python/3.0
Mercurial_ hg 1.1.2 http://code.python.org/hg/trunk/ http://code.python.org/hg/branches/py3k/ Mercurial_ hg 1.1.2 http://code.python.org/hg/trunk/ http://code.python.org/hg/branches/py3k/
git_ N/A 1.6.1 git://code.python.org/python/trunk git://code.python.org/python/branches/py3k git_ N/A 1.6.1 git://code.python.org/python/trunk git://code.python.org/python/branches/py3k
========== ========== ======= =================================== ========================================== ========== ========== ======= =================================== ==========================================
@ -1353,18 +1353,18 @@ repository is critical. If the difficulty or time is too great then a
person wishing to contribute to Python may very well give up. That person wishing to contribute to Python may very well give up. That
cannot be allowed to happen. cannot be allowed to happen.
I measured the checking out of code as if I was a non-core I measured the checking out of the 2.x trunk as if I was a non-core
developer. Timings were done using the ``time`` command in zsh and developer. Timings were done using the ``time`` command in zsh and
space was calculated with ``du -c -h``. space was calculated with ``du -c -h``.
======= ================ ============== ======= ================ ========= =====
DVCS Time Space DVCS San Francisco Vancouver Space
------- ---------------- -------------- ------- ---------------- --------- -----
svn 1:04 139 M svn 1:04 2:59 139 M
bzr 10:45 276 M bzr 10:45 23:51 276 M
hg 2:30 171 M hg 2:30 5:24 171 M
git 2:54 134 M git 2:54 5:28 134 M
======= ================ ============== ======= ================ ========= =====
.. note:: .. note::
The version of bzr running on code.python.org is 1.5. Changes were The version of bzr running on code.python.org is 1.5. Changes were
@ -1375,7 +1375,7 @@ When comparing these numbers to svn, it is important to realize that
it is not a 1:1 comparison. Svn does not pull down the entire revision it is not a 1:1 comparison. Svn does not pull down the entire revision
history like all of the DVCSs do. That means svn can perform an history like all of the DVCSs do. That means svn can perform an
initial checkout much faster than the DVCS purely based on the fact initial checkout much faster than the DVCS purely based on the fact
that it has less information to worry about. that it has less information to download for the network.
Performance of basic information functionality Performance of basic information functionality
@ -1420,7 +1420,10 @@ command usage. That is when I noticed ``git remote show``. Running
For hg, I never found the information I wanted on my own. It turns out For hg, I never found the information I wanted on my own. It turns out
I wanted ``hg paths``, but that was not obvious from the description I wanted ``hg paths``, but that was not obvious from the description
of "show definition of symbolic path names" as printed by ``hg help``. of "show definition of symbolic path names" as printed by ``hg help``
(it should be noted that reporting this in the PEP did lead to the
Mercurial developers to clarify the wording to make the use of the
``hg paths`` command clearer).
Updating a checkout Updating a checkout