Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

optimisations

X-seq: zsh-workers 9025
From: Adam Spiers <adam@xxxxxxxxxx>
To: zsh-workers@xxxxxxxxxxxxxx
Subject: optimisations
Date: Mon, 13 Dec 1999 19:24:57 +0000
In-reply-to: <991213182445.ZM11778@xxxxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: zsh-workers@xxxxxxxxxxxxxx
Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
References: <Liam.945065738.543685.31995.772540271@fizz> <991213182445.ZM11778@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Adam Spiers <adam@xxxxxxxxxx>

Bart Schaefer (schaefer@xxxxxxxxxxxxxxxxxxxxxxx) wrote:
> The last one is a bit unfortunate, but just "compinit" (without even
> trying any completions yet) adds half a megabyte to the RSS of zsh on
> my system, and it only goes up from there as functions autload and
> start caching their results in shell variables.

This reminds me.  Not only does the completion system make the
environment, and hence memory usage large, but it slows startup down.
Are there any significant optimisations which can be done?  Maybe
caching some of the large associative arrays to disk in (say) DBM
format so that several shells can share them?  I know this is already
done in .zcompdump ... any others?  (I've been meaning to do this for
_man, actually.)  I notice that $history gets set to the whole
history; what uses that?  I have HISTSIZE=5000 so this variable is
fairly sizeable!

Messages sorted by: Reverse Date, Date, Thread, Author