Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #78683

Re: "High water" Memory fragmentation still a thing?

From Marko Rauhamaa <marko@pacujo.net>
Newsgroups comp.lang.python
Subject Re: "High water" Memory fragmentation still a thing?
Date 2014-10-04 11:27 +0300
Organization A noiseless patient Spider
Message-ID <87d2a8s0iy.fsf@elektro.pacujo.net> (permalink)
References <CANm61jc=pB7n+5kuea6bmYXTbo3hXLT8d4JZx3Yq-TBtgGrFOQ@mail.gmail.com> <mailman.14595.1412404402.18130.python-list@python.org>

Show all headers | View raw


dieter <dieter@handshake.de>:

> Without memory compaction, long running processes tend to suffer from
> "memory fragmentation": while sufficient free memory is available, it
> is available only in small blocks, not large enough for some memory
> requests

Now this is a question for the computer scientists. The problem is quite
amenable to purely mathematical/statistical treatment. No doubt they've
been at it for decades.

My personal hunch is that GC in general works best with an ample amount
of RAM, where "ample" means, say, ten times the minimum amount needed.
As a bonus, I'm guessing the ample room would also all but remove the
memory fragmentation issue.


Marko

Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Re: "High water" Memory fragmentation still a thing? dieter <dieter@handshake.de> - 2014-10-04 08:33 +0200
  Re: "High water" Memory fragmentation still a thing? Marko Rauhamaa <marko@pacujo.net> - 2014-10-04 11:27 +0300
  Re: "High water" Memory fragmentation still a thing? bryanjugglercryptographer@yahoo.com - 2014-10-06 10:10 -0700

csiph-web