From: Anthony Liguori <aliguori@us.ibm.com>
To: Tommi Virtanen <tv@tv.debian.net>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: Serious performance issues
Date: Fri, 04 Mar 2005 09:52:13 -0600 [thread overview]
Message-ID: <4228842D.30505@us.ibm.com> (raw)
In-Reply-To: <42278833.6050500@tv.debian.net>
Tommi Virtanen wrote:
> I tested the disk, it still transfers ~50MB/s. I don't seem to be
> suffering from PIO mode. Also, things running from RAM cache are as
> slow as from disk.
What version of Xen is this?
> Any hints on what to try next?
If you're running xen-unstable, try xen-2.0.x or vice versa. Are you
absolutely positive that you've got enough memory allocated to dom0?
That you've got the proper IO chipset support built into the kernel?
That you've really got tls disabled (if you just move tls after an app
has already launched using it it will still be using it until you
restart the app)?
These numbers seem too bad to be Xen's fault alone. Do you have swap
enabled? Is there a great deal of swap activity?
Regards,
Anthony Liguori
> bw_mem
> -0.131072 1068.95
> +0.131072 4409.00
>
> bw_pipe
> -Pipe bandwidth: 85.42 MB/sec
> +Pipe bandwidth: 989.19 MB/sec
>
> bw_unix
> -AF_UNIX sock stream bandwidth: 104.75 MB/sec
> +AF_UNIX sock stream bandwidth: 968.87 MB/sec
>
> lat_ctx
> -"size=0k ovr=3.15
> -10 13.95
> +"size=0k ovr=1.09
> +10 0.94
>
> lat_fcntl
> -Fcntl lock latency: 43.2246 microseconds
> +Fcntl lock latency: 5.4676 microseconds
>
> lat_fifo
> -FIFO latency: 32.4076 microseconds
> +FIFO latency: 3.3622 microseconds
>
> lat_fs
> -0k 1000 18563 31549
> -1k 1000 6426 17887
> -4k 1000 6583 17826
> -10k 1000 3084 14989
> +0k 1000 63666 92541
> +1k 1000 24125 51193
> +4k 1000 25863 52089
> +10k 1000 12533 41564
>
> lat_pipe
> -Pipe latency: 31.0475 microseconds
> +Pipe latency: 5.4833 microseconds
>
> lat_proc
> -Process fork+exit: 789.2857 microseconds
> +Process fork+exit: 113.7347 microseconds
>
> lat_select
> -Select on 200 tcp fd's: 46.8159 microseconds
> +Select on 200 tcp fd's: 12.9369 microseconds
>
> lat_syscall
> -Simple syscall: 0.6188 microseconds
> +Simple syscall: 0.1547 microseconds
>
> lat_unix
> -AF_UNIX sock stream latency: 61.1547 microseconds
> +AF_UNIX sock stream latency: 21.7704 microseconds
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-04 15:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 21:57 Serious performance issues Tommi Virtanen
2005-03-04 15:52 ` Anthony Liguori [this message]
2005-03-04 18:55 ` Tommi Virtanen
-- strict thread matches above, loose matches on Subject: below --
2005-03-04 17:44 Ian Pratt
2005-03-07 6:51 ` Tommi Virtanen
2005-03-04 17:48 Ian Pratt
2005-03-04 18:57 ` Tommi Virtanen
2005-03-07 8:04 Ian Pratt
2005-03-07 7:11 ` Tommi Virtanen
2005-03-07 8:19 Ian Pratt
2005-03-07 9:23 ` Tommi Virtanen
2005-03-07 19:19 ` Nuutti Kotivuori
2005-03-07 9:47 Ian Pratt
2005-03-07 15:11 ` Nuutti Kotivuori
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=4228842D.30505@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=tv@tv.debian.net \
--cc=xen-devel@lists.sourceforge.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 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.