From: Eric Van Hensbergen <ericvh@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] interesting qemu problem
Date: Tue, 16 Mar 2010 18:47:36 -0500 [thread overview]
Message-ID: <4B6561F9-9D86-4B83-8ABE-13D00DABDABB@gmail.com> (raw)
In-Reply-To: <13426df11003161604t20c78a8btb4dc38bde0245c4e@mail.gmail.com>
On Mar 16, 2010, at 6:04 PM, ron minnich wrote:
> I was wrong. I built a new kernel from sources and performance is
> still very bad, with a load of 2500 minimum.
>
> Also, venti, on this little machine, is a bit hungry for memory.
> venti...2010/0316 20:31:06 venti: conf.../boot/venti: mem 1,048,576
> bcmem 140,753,578 icmem 211,130,368...httpd
> tcp!127.1!8000...init...icache 211,130,368 bytes = 3,298,912 entries;
> 16 scache
> sync...2010/0316 20:31:12 arenas01: indexing 430 clumps...
> announce tcp!127.1!17034...serving.
> fossil(#S/sdC0/fossil)...fsys: dialing venti at tcp!127.1!17034
>
>
> This image formerly ran in 256M, now requires 512M, because venti
> footprint is 140+211+211 ... wait, how does it ever fit in 512 anyway.
>
> I think qemu changed too. An old kernel has the same problems. Not
> sure what is up here. but for now qemu on unongo 9.10 is useless for
> plan 9 from what I can see.
>
You could configure venti to be less aggressive with its use of memory, but that would likely hurt performance.
Running venti inside qemu is silly. If you really want venti for your vm, run venti on the host and target your in-vm fossil at it.
-eric
next prev parent reply other threads:[~2010-03-16 23:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 17:29 ron minnich
2010-03-16 17:48 ` erik quanstrom
2010-03-16 18:19 ` ron minnich
2010-03-16 23:04 ` ron minnich
2010-03-16 23:07 ` erik quanstrom
2010-03-16 23:16 ` ron minnich
2010-03-18 13:54 ` blstuart
2010-03-16 23:47 ` Eric Van Hensbergen [this message]
2010-03-16 23:52 ` ron minnich
2010-03-16 23:55 ` erik quanstrom
2010-03-17 0:04 ` Eric Van Hensbergen
2010-03-17 0:22 ` ron minnich
2010-03-28 14:34 ` Georg Lehner
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=4B6561F9-9D86-4B83-8ABE-13D00DABDABB@gmail.com \
--to=ericvh@gmail.com \
--cc=9fans@9fans.net \
/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).