From: Dmitry Antipov <dmantipov@yandex.ru>
To: Glenn Morris <rgm@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel@gnu.org
Subject: Re: warn-maybe-out-of-memory
Date: Sun, 13 Jul 2014 11:01:44 +0400 [thread overview]
Message-ID: <53C22ED8.5050206@yandex.ru> (raw)
In-Reply-To: <5kpphafqd9.fsf@fencepost.gnu.org>
On 07/12/2014 09:17 PM, Glenn Morris wrote:
>> Here's another problem: what kind of "free memory" do you measure?
"Free" means "immediately available for allocation", i.e. not used by
OS or other processes for any purpose. If an OS should perform some
non-trivial action to get more memory (increase swap space or shrink
some internal data structures), this is not accounted as "free".
> I'd also like to know. If it really is the 8G amount in the example
> above, then as you say that seems just plain wrong for Emacs to warn
> about.
In the example above, I asked for 10G having just 8G free. In that example,
OS was able to shrink page cache by 2GB and satisfy the request; but we
can't assume that OS succeeds with this each time we ask to allocate a lot
of memory.
> Because who is opening a file with Emacs that matches the
> amount of RAM on their machine?
This is not uncommon editing task: as Google reports, users asks this question
after unsuccessful attempts to use their standard/favorite editors. For example:
http://askubuntu.com/questions/28847/text-editor-to-edit-4-3-gb-plain-text-file.
> The performance of Emacs is pretty poor with large files - the default
> large-file-warning-threshold is 10MB!
This may be subject to change without notice :-).
Dmitry
next prev parent reply other threads:[~2014-07-13 7:01 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 18:23 warn-maybe-out-of-memory Eli Zaretskii
2014-07-10 18:47 ` warn-maybe-out-of-memory Eli Zaretskii
2014-07-11 4:42 ` warn-maybe-out-of-memory Dmitry Antipov
2014-07-11 6:50 ` warn-maybe-out-of-memory Eli Zaretskii
2014-07-11 8:43 ` warn-maybe-out-of-memory Dmitry Antipov
2014-07-11 9:02 ` warn-maybe-out-of-memory Eli Zaretskii
2014-07-11 9:43 ` warn-maybe-out-of-memory Dmitry Antipov
2014-07-11 10:00 ` warn-maybe-out-of-memory Eli Zaretskii
2014-07-11 10:14 ` warn-maybe-out-of-memory Eli Zaretskii
2014-07-11 10:34 ` warn-maybe-out-of-memory Dmitry Antipov
2014-07-11 12:43 ` warn-maybe-out-of-memory Eli Zaretskii
2014-07-11 13:46 ` warn-maybe-out-of-memory Stefan Monnier
2014-07-12 17:17 ` warn-maybe-out-of-memory Glenn Morris
2014-07-13 7:01 ` Dmitry Antipov [this message]
2014-07-13 23:00 ` warn-maybe-out-of-memory Glenn Morris
2014-07-15 3:45 ` warn-maybe-out-of-memory Stefan Monnier
2014-07-15 4:44 ` warn-maybe-out-of-memory Dmitry Antipov
2014-07-17 3:59 ` warn-maybe-out-of-memory Stefan Monnier
2014-07-11 13:28 ` warn-maybe-out-of-memory Drew Adams
-- strict thread matches above, loose matches on Subject: below --
2014-07-10 18:22 warn-maybe-out-of-memory Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C22ED8.5050206@yandex.ru \
--to=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.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.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).