From: Nivedita Singhvi <niv@us.ibm.com>
To: Diwaker Gupta <diwaker.lists@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: n/w performance degradation
Date: Mon, 05 Dec 2005 18:15:35 -0800 [thread overview]
Message-ID: <4394F447.3040605@us.ibm.com> (raw)
In-Reply-To: <891be9410512051732i27e95cb3ue3bbfe8e58133895@mail.gmail.com>
Diwaker Gupta wrote:
> Not today. Unfortunately I'm going to be offline for the next couple
> of weeks. Anyhow, I'll try to see if I can post some more data in the
> interim.
No problem, thanks for running your tests again..
>>What are your memory allocations? How much
>>of a bump do you get if you increase memory?
>
>
> Currently, both dom0 and the vm have 128MB. I rebooted with dom0
> having 512MB and VM with 256 MB. Here are the numbers:
>
> dom0:
> [ 5] 0.0-10.0 sec 987 MBytes 828 Mbits/sec
>
> VM:
> [ 5] 0.0-10.0 sec 938 MBytes 787 Mbits/sec
>
> So getting slightly better. I haven't run these with SEDF though,
> above are using BVT.
Yep, the bigger difference in Xen 3.0 is that it's
just more sensitive to memory - when I tested
earlier in the summer most of the difference
between dom0 and domU could be gained back by
350MB dom0 and 512MB domUs doing heavy network
traffic.
So you have:
128MB domU - 450 Mbits/sec
250MB domU - 787 Mbits/sec
Which is roughly the same amount off the linear that I
recall..
thanks,
Nivedita
next prev parent reply other threads:[~2005-12-06 2:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 23:11 n/w performance degradation Diwaker Gupta
2005-12-05 23:23 ` Keir Fraser
2005-12-06 0:04 ` Diwaker Gupta
2005-12-06 11:20 ` Keir Fraser
2005-12-06 0:09 ` Nivedita Singhvi
2005-12-06 1:32 ` Diwaker Gupta
2005-12-06 2:15 ` Nivedita Singhvi [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-12-05 23:49 Ian Pratt
2005-12-06 0:06 ` Diwaker Gupta
2005-12-06 1:42 Ian Pratt
2005-12-06 2:07 ` Diwaker Gupta
2005-12-06 2:26 ` Nivedita Singhvi
2005-12-06 8:02 ` Diwaker Gupta
2005-12-06 10:42 Ian Pratt
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=4394F447.3040605@us.ibm.com \
--to=niv@us.ibm.com \
--cc=diwaker.lists@gmail.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.