From: Marius Storm-Olsen <marius@trolltech.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: msysGit <msysgit@googlegroups.com>
Subject: Performance on Windows (msysgit) with latest patches
Date: Tue, 14 Aug 2007 11:18:20 +0200 [thread overview]
Message-ID: <46C1735C.4050701@trolltech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2876 bytes --]
Hi,
After all the performance patches that has been commited to the
git.git/master branch, I figured it would be interesting to check out
how it would affect times on Windows. So, I merged the git.git/master
branch into the 4msysgit.git/next branch and ran the scripts which Moe
provided. The result you'll find below.
git-status got a 1.6X speed-up, and git-commit on a single file got a
2.5X speed-up. However, git-add and git-commit of all 100K files got a
slight slowdown.
Before After
performance patches performance patches
------------------------- -------------------------
Command: git init Command: git init
------------------------- -------------------------
real 0m0.031s real 0m0.032s
user 0m0.031s user 0m0.015s
sys 0m0.000s sys 0m0.015s
------------------------- -------------------------
Command: git add . Command: git add .
------------------------- -------------------------
real 0m19.328s real 0m20.204s
user 0m0.015s user 0m0.015s
sys 0m0.015s sys 0m0.000s
------------------------- -------------------------
Command: git commit -a... Command: git commit -a...
------------------------- -------------------------
real 0m30.937s real 0m31.328s
user 0m0.015s user 0m0.015s
sys 0m0.015s sys 0m0.015s
------------------------- -------------------------
3x Command: git-status 3x Command: git-status
------------------------- -------------------------
real 0m19.531s real 0m12.016s
user 0m0.211s user 0m0.274s
sys 0m0.136s sys 0m0.091s
real 0m19.532s real 0m12.016s
user 0m0.259s user 0m0.242s
sys 0m0.091s sys 0m0.137s
real 0m19.593s real 0m12.000s
user 0m0.211s user 0m0.227s
sys 0m0.152s sys 0m0.090s
------------------------- -------------------------
Command: git commit... Command: git commit...
(single file) (single file)
------------------------- -------------------------
real 0m36.688s real 0m14.640s
user 0m0.031s user 0m0.015s
sys 0m0.000s sys 0m0.000s
Total time -------------- Total time --------------
Real time: 2m 25.703s Real time: 1m 42.358s
- User time: 0m 0.031s - User time: 0m 0.015s
- Kernel time: 0m 0.031s - Kernel time: 0m 0.078s
= Idle time: 2m 25.640s = Idle time: 1m 42.264s
------------------------- -------------------------
--
.marius
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]
next reply other threads:[~2007-08-14 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 9:18 Marius Storm-Olsen [this message]
2007-08-14 16:22 ` Performance on Windows (msysgit) with latest patches Linus Torvalds
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=46C1735C.4050701@trolltech.com \
--to=marius@trolltech.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.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).