Author neologix
Recipients josh.r, jtaylor, neologix, njs, pitrou, skrah, vstinner
Date 2014-04-27.18:36:51
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAH_1eM061WVF10O6YmMMY2ecG9AM0zv-daucCovG81FfizQ2zQ@mail.gmail.com>
In-reply-to <1398623251.49.0.459241305179.issue21233@psf.upfronthosting.co.za>
Content
> So yeah, touching pages can affect whether a later malloc returns ENOMEM.
>
> I'm not sure any of this actually matters in the Python case though :-). There's still no reason to go touching pages pre-emptively just in case we might write to them later -- all that does is increase the interpreter's memory footprint, which can't help anything. If people are worried about overcommit, then they should turn off overcommit, not try and disable it on a piece-by-piece basis by trying to get individual programs to memory before they need it.

Absolutely: that's why I'm really in favor of exposing calloc, this
could definitely help many workloads.

Victor, did you run any non-trivial benchmark, like pybench & Co?

As I said, I'm not expecting any improvement, I just want to make sure
there's not hidden regression somewhere (like the one for GC-tracked
objects above).
History
Date User Action Args
2014-04-27 18:36:51neologixsetrecipients: + neologix, pitrou, vstinner, njs, skrah, jtaylor, josh.r
2014-04-27 18:36:51neologixlinkissue21233 messages
2014-04-27 18:36:51neologixcreate