git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Carlos Pita" <carlosjosepita@gmail.com>,
	"“git@vger.kernel.org”" <git@vger.kernel.org>,
	"SZEDER Gábor" <szeder.dev@gmail.com>
Subject: Re: Index files autocompletion too slow in big repositories (w / suggestion for improvement)
Date: Mon, 17 Apr 2017 10:03:56 +0200	[thread overview]
Message-ID: <2304c00a-ed87-7119-3753-95f61bcf28f6@kdbg.org> (raw)
In-Reply-To: <xmqqefwrk7ao.fsf@gitster.mtv.corp.google.com>

Am 17.04.2017 um 06:05 schrieb Junio C Hamano:
> Johannes Sixt <j6t@kdbg.org> writes:
>> This is about command line completion. We go a long way to avoid
>> forking processes there. What is 10x faster on Linux despite of
>> forking a process may not be so on Windows.
>
> Doesn't this depend on how many paths there are?  If there are only
> a few paths, the loop in shell would beat a pipe into sed even on
> Linux, I suspect, and if there are tons of paths, at some number,
> loop in shell would become slower than a single spawning of sed on
> platforms with slower fork, no?

Absolutely. I just want to make sure a suggested change takes into 
account the situation on Windows, not only the "YESSSS!" and "VERY 
WELL!" votes of Linux users ;)

-- Hannes


  reply	other threads:[~2017-04-17  8:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 20:06 Index files autocompletion too slow in big repositories (w / suggestion for improvement) Carlos Pita
2017-04-14 22:08 ` Carlos Pita
2017-04-14 22:33   ` Ævar Arnfjörð Bjarmason
2017-04-15  1:37     ` Jacob Keller
2017-04-15  7:52       ` Junio C Hamano
2017-04-15 11:59     ` Johannes Sixt
2017-04-16  0:31       ` Jacob Keller
2017-04-17  4:05       ` Junio C Hamano
2017-04-17  8:03         ` Johannes Sixt [this message]
2017-04-15 12:30     ` Johannes Sixt

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2304c00a-ed87-7119-3753-95f61bcf28f6@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=avarab@gmail.com \
    --cc=carlosjosepita@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=szeder.dev@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).