git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fredrik Gustafsson <iveqy@iveqy.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Fredrik Gustafsson <iveqy@iveqy.com>,
	spearce@spearce.org, git@vger.kernel.org, pclouds@gmail.com,
	Jeff King <peff@peff.net>
Subject: Re: [RFC] Add posibility to preload stat information.
Date: Wed, 20 Mar 2013 18:41:20 +0100	[thread overview]
Message-ID: <20130320174120.GA32426@paksenarrion.iveqy.com> (raw)
In-Reply-To: <CALkWK0=b80U5dxGMpwKwL+jFURisEuSapWuuNRFcP+5R2f3+GA@mail.gmail.com>

On Wed, Mar 20, 2013 at 10:45:22PM +0530, Ramkumar Ramachandra wrote:
> Fredrik Gustafsson wrote:
> > When entering a git working dir, optionally run a forked process that
> > stat all files in the whole workdir and therefore loads stat information
> > to RAM which will speedup things like git status and so on.
> 
> This is misleading.  You just execute the equivalent of `git status`
> everytime I request a prompt inside a git working directory.  And this
> is if I'm using __git_ps1() to augment my prompt, which I'm not- I use
> ZSH's vcs_info, which is arguably better.  Also, you forgot to say how
> to turn on the feature.

The invokation place is quesionable (Junio also had some thoughts about
that). I don't find vcs_info in the contrib/completition/. Do you have
any suggestion about where the best way is to inwoke this kind of thing?

I added documentation about how to turn the feature on, in the same way
the other features is documented. (Is there an other way/better way I
should do this?)

> 
> That said, this feature is extremely gross; it thrashes my filesystem
> and hard drive.  Modern software is written to minimize IO, not
> maximize it!  I'm completely against the inclusion of this patch.

It's extremly gross. I don't like this, _but_ it does speed up my work.
I'm unsure if it should be included in git though (hence the RFC-tag).

> 
> However, I would not mind a feature that runs `git status` the very
> first time I enter a git working directory: when I enter my clone of
> linux.git, it takes my first `git status` invocation a good ten
> seconds to complete, and we can fix this pretty easily.

That's the problem I try to solve. However "the first time" is
irrelevant. We will run git status a bit before we need it. If we enter
linux.git, do other work (in an other project) for an hour and go back
to linux.git our cache will probably be empty. We will need to run this
more than "the first time". But still, we don't want it to run too
often. (Which is does now).

-- 
Med vänliga hälsningar
Fredrik Gustafsson

tel: 0733-608274
e-post: iveqy@iveqy.com

  reply	other threads:[~2013-03-20 17:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 12:15 [RFC] Add posibility to preload stat information Fredrik Gustafsson
2013-03-20 16:48 ` Jeff King
2013-03-20 17:15   ` Junio C Hamano
2013-03-20 17:47     ` Jeff King
2013-03-21 10:41       ` Thomas Rast
2013-03-21 14:44         ` Junio C Hamano
2013-03-30 19:42           ` Phil Hord
2013-03-20 18:40   ` Fredrik Gustafsson
2013-03-20 17:15 ` Ramkumar Ramachandra
2013-03-20 17:41   ` Fredrik Gustafsson [this message]
2013-03-20 17:49     ` Ramkumar Ramachandra
2013-03-20 18:36       ` Fredrik Gustafsson
2013-03-20 18:46         ` Jeff King

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=20130320174120.GA32426@paksenarrion.iveqy.com \
    --to=iveqy@iveqy.com \
    --cc=artagnon@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=spearce@spearce.org \
    /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).