From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: autoload
Date: Tue, 23 Dec 2014 09:36:58 -0800 [thread overview]
Message-ID: <141223093658.ZM10109@torch.brasslantern.com> (raw)
In-Reply-To: <54998F77.3050903@eastlink.ca>
On Dec 23, 7:51am, Ray Andrews wrote:
}
} Can we determine how much memory functions use when loaded, such that a
} practical determination might be made as to how much 'real' difference
} it might make to free memory vs. any speed considerations?
The in-memory size of a function is at least as large and probably a bit
larger than its on-disk size as a file, because it's stored in both
compiled and text form (the former for speed, the latter for output of
the verbose and xtrace options and/or the functions command).
} What do guys do in the real world?
I autoload practically everything. I don't, however, zcompile things
very much.
next prev parent reply other threads:[~2014-12-23 17:36 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 15:51 autoload Ray Andrews
2014-12-23 17:36 ` Bart Schaefer [this message]
2014-12-23 18:19 ` autoload Ray Andrews
2015-09-08 12:32 Announce of Zsh Navigation Tools Sebastian Gniazdowski
2015-09-12 17:50 ` Ray Andrews
2015-09-12 19:41 ` ZyX
2015-09-12 21:03 ` Ray Andrews
2015-09-12 22:10 ` Bart Schaefer
2015-09-12 23:03 ` Ray Andrews
2015-09-12 23:43 ` Bart Schaefer
2015-09-14 2:14 ` autoload Ray Andrews
2015-09-14 2:38 ` autoload Bart Schaefer
2015-09-14 3:34 ` autoload Ray Andrews
2015-09-14 20:21 ` autoload Bart Schaefer
2015-09-15 2:48 ` autoload Ray Andrews
2015-09-15 3:48 ` autoload Bart Schaefer
2015-09-15 16:18 ` autoload Ray Andrews
2015-09-16 4:09 ` autoload Ray Andrews
2015-09-17 15:54 autoload Ray Andrews
2015-09-17 17:34 ` autoload Bart Schaefer
2015-09-17 19:22 ` autoload Ray Andrews
2015-09-17 20:40 ` autoload Bart Schaefer
2015-09-17 23:06 ` autoload Ray Andrews
2015-09-17 23:20 ` autoload Bart Schaefer
2015-09-18 1:20 ` autoload Ray Andrews
2015-09-18 4:04 ` autoload Bart Schaefer
2015-09-18 5:00 ` autoload Ray Andrews
2015-09-18 5:52 ` autoload Bart Schaefer
2015-09-18 15:49 ` autoload Ray Andrews
2015-09-18 16:52 ` autoload Bart Schaefer
2015-09-18 18:29 ` autoload Ray Andrews
2015-09-18 19:02 ` autoload Bart Schaefer
2015-09-18 22:57 ` autoload Ray Andrews
2015-09-19 0:14 ` autoload Bart Schaefer
2015-09-19 15:04 ` autoload Ray Andrews
2015-09-19 16:29 ` autoload Bart Schaefer
2015-09-19 18:13 ` autoload Ray Andrews
2015-09-19 21:22 ` autoload Bart Schaefer
2015-09-19 22:12 ` autoload Ray Andrews
2015-09-20 5:53 ` autoload Bart Schaefer
2015-09-20 15:37 ` autoload Ray Andrews
2015-09-20 15:59 ` autoload Bart Schaefer
2015-09-20 0:58 ` autoload Ray Andrews
2015-09-20 5:41 ` autoload Bart Schaefer
2015-09-20 23:21 ` autoload Ray Andrews
2015-09-21 4:18 ` autoload Bart Schaefer
2015-09-21 17:03 ` autoload Ray Andrews
2015-09-21 18:17 ` autoload Bart Schaefer
2015-09-21 20:09 ` autoload Ray Andrews
2015-09-22 3:19 ` autoload Bart Schaefer
2015-09-22 17:33 ` autoload Ray Andrews
2015-09-23 4:39 ` autoload Bart Schaefer
2015-09-23 15:06 ` autoload Ray Andrews
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=141223093658.ZM10109@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).