From: cinap_lenrek@gmx.de
To: 9front@googlegroups.com
Subject: Re: memory usage of installer
Date: Thu, 16 Jun 2011 16:47:51 +0200 [thread overview]
Message-ID: <faef2461227d50d2f216db4bb38036f6@gmx.de> (raw)
In-Reply-To: <08809ae7-8156-4b97-8cd6-e87e4e4618c2@g12g2000yqd.googlegroups.com>
yep, thats plausible. i'm looking into where cwfs allocates his memory.
we have a fixed overhead of arround 13MB that is not taken into account
in that sysmem/4 formula.
i'm still not sure why it allocates more memory at runtime. the only
place right now where this could happen are message buffers.
more analyzing is required before action can be taken.
--
cinap
next prev parent reply other threads:[~2011-06-16 14:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 11:51 suharik
2011-06-16 12:12 ` cinap_lenrek
2011-06-16 14:15 ` suharik
2011-06-16 14:47 ` cinap_lenrek [this message]
2011-06-16 16:16 ` cinap_lenrek
2011-06-16 18:09 ` cinap_lenrek
2011-06-16 18:45 ` cinap_lenrek
2011-06-16 20:47 ` suharik
2011-06-16 23:46 ` cinap_lenrek
2011-06-16 23:49 ` ron minnich
2011-06-17 2:44 ` Iruatã Souza
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=faef2461227d50d2f216db4bb38036f6@gmx.de \
--to=cinap_lenrek@gmx.de \
--cc=9front@googlegroups.com \
/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;
as well as URLs for NNTP newsgroup(s).