From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: [RFC] i18n.pathencoding
Date: Wed, 05 Sep 2012 21:52:42 +0200 [thread overview]
Message-ID: <5047AD8A.3020203@web.de> (raw)
In-Reply-To: <7vy5kp8s3h.fsf@alter.siamese.dyndns.org>
On 04.09.12 22:12, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>> This leads to 2 questions:
>> a) Do we want the reencode feature in git, so that I continue to work on it?
>> From a performance point of view that would probably OK:
>> The "git status" on a linux tree was slightly slower on my PC when measured with time.
>> From the user experience there was not a difference.
>
> I am not fundamentally opposed to such a change, as long as the
> change does not affect performance at all when the feature is not
> used, and the resulting code does not become too ugly.
>
> Use of the "reencode" feature may have to make things slow, but you
> have to spend some cycle to do what the feature has to do anyway,
> so...
>
>> b) If yes,
>> I have to admit that I don't use paths from --stdin or file so much,
>> except "git am" or "git format-patch"
>> Which commands are affected?
>
> $ git grep -l -e '--stdin' Documentation/git*
>
> may be a good starting point.
------------------------------
I'll have a look into the --stdin stuff later, thanks Junio
-------------------------------
And here some benchmarks on my PC,
first run is using git v1.7.12,
second run with i18n.pathencoding applied
===================
for f in 1 2 3 4 5; do time git status ; done 2>&1 | egrep "^user|^real|^sys"
real 0m0.492s
user 0m0.300s
sys 0m0.200s
real 0m0.448s
user 0m0.260s
sys 0m0.190s
real 0m0.443s
user 0m0.250s
sys 0m0.200s
real 0m0.451s
user 0m0.260s
sys 0m0.190s
real 0m0.429s
user 0m0.230s
sys 0m0.200s
=========================
for f in 1 2 3 4 5; do time ~/projects/git/tb.localfname/git status ; done 2>&1 | egrep "^user|^real|^sys"
real 0m0.580s
user 0m0.320s
sys 0m0.230s
real 0m0.461s
user 0m0.260s
sys 0m0.200s
real 0m0.463s
user 0m0.250s
sys 0m0.220s
real 0m0.445s
user 0m0.290s
sys 0m0.160s
real 0m0.443s
user 0m0.240s
sys 0m0.210s
=======================
It seems that we have a little penalty on performance.
I'll have a look at the readdir() function.
next prev parent reply other threads:[~2012-09-05 19:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-01 6:11 [RFC] i18n.pathencoding Torsten Bögershausen
2012-09-02 22:59 ` Robin Rosenberg
2012-09-08 10:09 ` Torsten Bögershausen
2012-09-04 12:23 ` Nguyen Thai Ngoc Duy
2012-09-04 17:19 ` Junio C Hamano
2012-09-04 19:51 ` Torsten Bögershausen
2012-09-04 20:12 ` Junio C Hamano
2012-09-05 19:52 ` Torsten Bögershausen [this message]
2012-09-05 11:11 ` Nguyen Thai Ngoc Duy
2012-09-05 19:49 ` Torsten Bögershausen
2012-09-06 3:24 ` Junio C Hamano
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=5047AD8A.3020203@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).