git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC] i18n.pathencoding

From
Torsten Bögershausen <tboegi@web.de>
Date
Sep 5, 2012, 19:52 UTC
Message-ID
<5047AD8A.3020203@web.de>
In-Reply-To
<7vy5kp8s3h.fsf@alter.siamese.dyndns.org>
On 04.09.12 22:12, Junio C Hamano wrote:
Show 24 quoted lines
> 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.

Previous: Junio C HamanoNext: Nguyen Thai Ngoc Duy
Message 8 of 11 in “[RFC] i18n.pathencoding”
  1. Torsten BögershausenSep 1, 2012
  2. Robin RosenbergSep 2, 2012
  3. Torsten BögershausenSep 8, 2012
  4. Nguyen Thai Ngoc DuySep 4, 2012
  5. Junio C HamanoSep 4, 2012
  6. Torsten BögershausenSep 4, 2012
  7. Junio C HamanoSep 4, 2012
  8. Torsten BögershausenSep 5, 2012
  9. Nguyen Thai Ngoc DuySep 5, 2012
  10. Torsten BögershausenSep 5, 2012
  11. Junio C HamanoSep 6, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.