From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: Improving zcompdump (Re: A patch with hashtable optimization, which doesn't work)
Date: Sat, 3 Jun 2017 17:54:49 -0700 [thread overview]
Message-ID: <170603175449.ZM16110@torch.brasslantern.com> (raw)
In-Reply-To: <etPan.5932c380.2ae8944a.a149@MacMini.local>
On Jun 3, 4:11pm, Sebastian Gniazdowski wrote:
} Subject: Re: Improving zcompdump (Re: A patch with hashtable optimization,
}
} On 20 maja 2017 at 19:08:09, Bart Schaefer (schaefer@brasslantern.com) wrote:
} > How much does zcompdump actually help? Have you compared startup with
} > and without it?
Haven't seen that yet (nor tried it myself, tho).
} > One lesson learned with Completion/Base/Utility/_store_cache is that
} > parsing array assignments is expensive.
}
} Results seem to confirm what you said
I also tried something similar ... using the just the default set of
completions, more wall-clock time is spent restoring the autoloads
than loading the _comps array, at least on my system.
next prev parent reply other threads:[~2017-06-04 0:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-03 14:11 Sebastian Gniazdowski
2017-06-04 0:54 ` Bart Schaefer [this message]
2017-06-04 7:18 ` Sebastian Gniazdowski
-- strict thread matches above, loose matches on Subject: below --
2017-05-18 10:14 A patch with hashtable optimization, which doesn't work Sebastian Gniazdowski
2017-05-18 12:16 ` Sebastian Gniazdowski
2017-05-20 5:06 ` Sebastian Gniazdowski
2017-05-20 17:08 ` Improving zcompdump (Re: A patch with hashtable optimization, which doesn't work) Bart Schaefer
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=170603175449.ZM16110@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--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).