Re: [Xen-users] IO performance testing between dom0 and guests

["Filip Sergeys" <filip.sergeys@xxxxxxxxxxxxxxxx>]

I couldn't get xen-U kernel for SuSE with modules support to  work properly yet, so I build an "all in" kernel for testing.
THe bug fixes in xen-2.0-testing for block IO are TREMENDIOUSLY GREAT:

xen-2.0.4 bonnie++ -d /var/maxdb -r 10 -s 400 -n 0 -u root
--------------------------------------------------------------------

Version 1.01d       ------Sequential Output------ --Sequential Input- 
--Random- 
                     -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- 
--Seeks-- 
 Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP 
 staging        400M 132810  96 48009  11 53177   5 120590  99 +++++ +++ 623.1   0



 xen-2.0-testing bonnie++ -d /var/maxdb -r 10 -s 400 -n 0 -u root
--------------------------------------------------------------------------
Version 1.01d       ------Sequential Output------ --Sequential Input- --Random-
                    -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks--
Machine        Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP  /sec %CP
staging        400M 134499  98 184713  42 70006   3 115162  99 +++++ +++  1621   0

staging,400M,134499,98,184713,42,70006,3,115162,99,+++++,+++,1620.6,0,,,,,,,,,,,,,

See the block sequential output: 48009 before, now 184713 !!! wow great work. (I repeated the tests a few times, and the results are more or less the same every time)

Also the queries are running way faster, need to do benchmarks on them too

Next step, get to compile a xen-U  kernel for SuSE with modules support

Thanx so far

Greetz

Filip 


On Fri, 2005-04-08 at 19:59, Mark Williamson wrote:
> Did you get a reply to this?
>
> You want to put an "initrd=" line in your config file.
>
> Chroot seems like the most straightforward solution but you should probably 
> tell mkinitrd explicitly the name of the SuSE Xen kernel anyhow.  You'll need 
> to copy the initrd out into the dom0 filesystem and unmount the guest 
> filesystem before starting the domain (Xend has to be able to find it, 
> according to the path specified in the config).
>
> Bootsplash etc won't matter for a domU, so you can probably just ignore it.
>
> /me goes to watch Doctor Who now :-)
>
> HTH,
> Mark
>
> On Thursday 07 April 2005 18:20, you wrote:
> > I downloaded, untarred, build and installed the xen-2.0-testing kernel.
> > However I still have a small question (actually a few small questions):
> > This time I used the SuSE original configfile to build the unpriviledged
> > kernel.
> > This kernel loads almost everything from modules, so it needs an initrd.
> > Here are my questions?
> > Where do build the initrd for the unpriviledged domain?
> >      - in the dom0 under debian
> >      - under the guest os (SuSE), by mounting the guest OS partition,
> > chroot to it, copy the dom0 /lib/modules/2.6.11-xenU directory from dom0
> > to guest and then run the mkinitrd?
> >
> > Where should I store that initrd?
> >     - in /boot from dom0
> >     - in /boot from guest
> >
> > How do I make clear in /etc/xen/staging (config file for my guest called
> > staging) that an initrd is needed?
> >
> > What parameters would you use in your mkinitrd? For what is have read,
> > bootsplash should be avoided with -s off.
> >
> > Thanks in advance,
> >
> > Greetz,
> >
> > Filip
> >
> >
> > On Thu, 2005-04-07 at 14:43, M.A. Williamson wrote:
> >
> >     You should find big improvements in the testing tree - there have been
> >     several recent bug fixes relating to block IO.
> >
> >     Cheers,
> >     Mark
> >
> >     On Apr 7 2005, Filip Sergeys wrote:
> >     > (Message body was not text: suppressed)
> >
> >     _______________________________________________
> >     Xen-users mailing list
> >     Xen-users@xxxxxxxxxxxxxxxxxxx
> >
> > http://lists.xensource.com/xen-users
>

-- 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
* System Engineer, Verzekeringen NV *
* www.verzekeringen.be              *
* Oostkaai 23 B-2170 Merksem        *
* 03/6416673 - 0477/340942          *
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users