Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Marko Rauhamaa Newsgroups: comp.lang.python Subject: Re: "High water" Memory fragmentation still a thing? Date: Sat, 04 Oct 2014 11:27:01 +0300 Organization: A noiseless patient Spider Lines: 18 Message-ID: <87d2a8s0iy.fsf@elektro.pacujo.net> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx05.eternal-september.org; posting-host="ff5cf27ef3d5b31f034d3b72bdc27a41"; logging-data="1079"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+X1wmMtcrI33nTm3mBRniG" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) Cancel-Lock: sha1:gFgRwUMp22tUeliDFLpny+ksnJk= sha1:wQzpHoW3EfpYDc1itxwTpPvUp9k= Xref: csiph.com comp.lang.python:78683 dieter : > 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