From: Glenn Morris <rgm@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,
Dmitry Antipov <dmantipov@yandex.ru>,
emacs-devel@gnu.org
Subject: Re: warn-maybe-out-of-memory
Date: Sat, 12 Jul 2014 13:17:54 -0400 [thread overview]
Message-ID: <5kpphafqd9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: jwv61j4j9u9.fsf-monnier+emacs@gnu.org
Stefan Monnier wrote:
>> This depends on OS and VM pressure. For example, on GNU/Linux if I have
>> just slightly above 8G free:
>
>> $ free
>> total used free shared buffers cached
>> Mem: 16127204 7762072 8365132 68248 84396 6401276
>> -/+ buffers/cache: 1276400 14850804
>
> Here's another problem: what kind of "free memory" do you measure?
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. If it subtracts off the cache, that's still wrong if you have any
swap space. The total memory is not wrong, but frankly seems completely
pointless. Because who is opening a file with Emacs that matches the
amount of RAM on their machine? The performance of Emacs is pretty poor
with large files - the default large-file-warning-threshold is 10MB!
next prev parent reply other threads:[~2014-07-12 17:17 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 ` Glenn Morris [this message]
2014-07-13 7:01 ` warn-maybe-out-of-memory Dmitry Antipov
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=5kpphafqd9.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=dmantipov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).