From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [bitbake-devel] Bitbake Memory Usage
Date: Sun, 19 Feb 2012 08:34:36 +0000 [thread overview]
Message-ID: <1329640476.2591.149.camel@x121e.pbcl.net> (raw)
In-Reply-To: <1329620128.7006.8.camel@ted>
On Sun, 2012-02-19 at 02:55 +0000, Richard Purdie wrote:
> The problem is then going to be memory fragmentation since whilst we can
> free the memory used by the objects, its extremely unlikely everything
> to the end of the data segment is likely to be free so sbrk() cannot be
> rolled backwards to free memory.
Sounds like it. Have you tried running python with a lower
MMAP_THRESHOLD?
p.
next prev parent reply other threads:[~2012-02-19 8:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-18 23:36 Bitbake Memory Usage Richard Purdie
2012-02-19 2:55 ` [bitbake-devel] " Richard Purdie
2012-02-19 8:34 ` Phil Blundell [this message]
2012-02-19 15:41 ` Richard Purdie
2012-02-19 16:04 ` Phil Blundell
2012-02-20 14:05 ` Colin Walters
2012-02-20 19:57 ` Chris Larson
2012-02-21 22:15 ` [bitbake-devel] " Richard Purdie
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=1329640476.2591.149.camel@x121e.pbcl.net \
--to=philb@gnu.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=openembedded-core@lists.openembedded.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox