From: "Peter Grayson" <pete@jpgrayson.net>
To: "Daniel Shahaf" <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH] Remove StGit patch detection from vcs_info
Date: Sun, 13 Nov 2022 22:38:50 -0500 [thread overview]
Message-ID: <aaf82ac8-f7db-46e9-9995-d4a6dde1e5d9@app.fastmail.com> (raw)
In-Reply-To: <20221113043040.GG27622@tarpaulin.shahaf.local2>
On Sat, Nov 12, 2022, at 11:30 PM, Daniel Shahaf wrote:
> Peter Grayson wrote on Sat, Nov 12, 2022 at 09:46:02 -0500:
>> On Fri, Nov 11, 2022, at 6:49 AM, Daniel Shahaf wrote:
>> > [re #2]: It sounds like StGit 2.x support can be implemented at the cost
>> > of one fork(2) for those who don't use StGit and under a microsecond for
>> > those who do. That doesn't sound like a deal breaker at all.
>>
>> Running `stg series` with StGit 2.0 takes about 12ms in my environment.
>> StGit 1.5 it is about 32ms. Not a microsecond, but perhaps acceptable
>> nonetheless.
>>
>
> To be clear, are these figures the duration of the «stg series
> --noprefix --applied» invocation?
Yes.
> What's the impact on people who don't have stg(1) installed, or who have
> stg(1) installed but are currently in a worktree that doesn't use StGit?
> I.e., are those figures immediately after `git init`, or in a worktree
> that has a StGit patch stack, or?
Without stg(1) installed, the cost would be however long it takes zsh to
determine that the executable is not available in $path, which is
ostensibly very fast (microseconds?).
If stg(1) is installed, but run in a repo with a branch that has not been
initialized with `stg init`, it's still about 12ms. Almost all that time
is taken just to initialize a libgit2 Repository structure, which is
used to interrogate the object database to determine whether a StGit
stack is initialized.
> In general, 32ms for everyone might be too much (what if another
> third-party tool wanted to do its own elif branch that also spent 32ms
> for everyone? That'd be 64ms in total and counting…).
Well, that was my original thought as well and why my first patch simply
removed StGit support from vcs_info. Note that 32ms is on a particularly
fast machine and I stand by my assertion that Python startup time can be
on the order of hundreds of milliseconds on more modest machines and/or
with older versions of Python.
> However, if the 32ms would only be seen by users of an EOL'd stg(1),
> we can relax the threshold a bit. On the other hand, if it's 32ms
> just in cases where stg(1) is used… well, there doesn't seem to be
> much we /can/ do there.
The relevant scenarios:
* stg(1) not installed => ~free
* stg(1) < 2.0 installed => 30+ ms
* stg(1) >= 2.0 installed => ~10 ms
The worst case scenario would be for someone where stg(1) <2.0 is
installed, but not used. This would create overhead in vcs_info without
any value for the user. All other scenarios seem to end up with the
user getting what they paid for.
> Perhaps hide some or all of the work behind an opt-in switch. (For
> instance, the default settings show only the topmost applied patch, so
> if it's possible to tell stg(1) not to emit any other patches, that
> might help the code finish more quickly.)
Limiting the output to only the topmost patch will not have a material
effect on the runtime because of how the overhead is dominated by
libgit2 initialization. So an opt-in switch would have be all or
nothing; either try to run stg(1) or not.
Also worth noting is that changing StGit support in vcs_info opt-in
would be a bit of a regression and would add more configuration
surface area. Not sure if/how the zsh project does versioning for
something like this. I did not include such a switch in my latest
patch because of these issues.
> From the "Is your computer plugged in?" department: Is that 32ms figure
> on hot disk cache with .pyc files already having been generated?
Yes. I used hyperfine(1) to do these measurements.
Pete
next prev parent reply other threads:[~2022-11-14 3:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 20:43 [PATCH] Remove _stgit completion script Peter Grayson
2022-10-31 9:19 ` Daniel Shahaf
2022-10-31 10:13 ` StGit 2.0 and vcs_info (was: Re: [PATCH] Remove _stgit completion script) Daniel Shahaf
2022-11-01 3:00 ` [PATCH] Remove _stgit completion script Peter Grayson
2022-11-01 3:04 ` [PATCH] Remove StGit patch detection from vcs_info Peter Grayson
2022-11-11 11:49 ` Daniel Shahaf
2022-11-12 14:46 ` Peter Grayson
2022-11-12 15:42 ` [PATCH] Updated StGit patch detection in vcs_info Peter Grayson
2022-11-13 4:58 ` Daniel Shahaf
2022-11-16 20:45 ` [PATCH v2] " Peter Grayson
2022-12-08 14:52 ` [PATCH v3] " Peter Grayson
2022-12-08 22:06 ` Daniel Shahaf
2022-12-08 22:08 ` [PATCH] vcs_info git: Check the get-unapplied style as documented (was: [PATCH v3] Updated StGit patch detection in vcs_info) Daniel Shahaf
2022-12-09 0:59 ` [PATCH v3] Updated StGit patch detection in vcs_info Peter Grayson
2022-12-09 1:37 ` Daniel Shahaf
2022-12-10 12:55 ` Peter Grayson
2022-12-10 13:31 ` Daniel Shahaf
2022-11-13 4:30 ` [PATCH] Remove StGit patch detection from vcs_info Daniel Shahaf
2022-11-14 3:38 ` Peter Grayson [this message]
2022-11-14 5:17 ` Mikael Magnusson
2022-11-14 13:21 ` Daniel Shahaf
2022-11-14 13:15 ` Daniel Shahaf
2022-11-16 19:38 ` Peter Grayson
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=aaf82ac8-f7db-46e9-9995-d4a6dde1e5d9@app.fastmail.com \
--to=pete@jpgrayson.net \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-workers@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).