From: Dmitry Antipov <dmantipov@yandex.ru>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: warn-maybe-out-of-memory
Date: Tue, 15 Jul 2014 08:44:27 +0400 [thread overview]
Message-ID: <53C4B1AB.8010402@yandex.ru> (raw)
In-Reply-To: <jwv61izb86o.fsf-monnier+emacs@gnu.org>
On 07/15/2014 07:45 AM, Stefan Monnier wrote:
> Freeing space from the cache is a trivial action.
AFAICS on Linux, this is not true - in my tests, huge allocations
may be 20% slower when the kernel should reclaim cache space first.
This may be even slower if an OS has to increase swap space
(according to Eli, this may happen on MS-Windows).
> The OS wants to keep as much stuff in the cache as it can, thus
> minimizing the "free" space, since "free" here basically means "wasted".
This depends on usage patterns. If you interleave I/O and relatively
large allocations, it's fairly unreasonable to fill almost all memory
with cached data just to throw it away very soon.
> If your "free" includes "free in RAM + free in swap" then it's
> marginally more useful ("free in RAM" will usually be close to 0,
> whereas "free in swap" should usually be fairly large), but I still
> can't think of a frequent enough configuration and situation where this
> would be useful enough to justify wasting code on it.
This is not expected to be frequent.
Dmitry
next prev parent reply other threads:[~2014-07-15 4:44 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 ` 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 ` Dmitry Antipov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53C4B1AB.8010402@yandex.ru \
--to=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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.