WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] memory not released to dom0

On Tue, Jan 26, 2010 at 06:16:26PM +0700, Fajar A. Nugraha wrote:
> On Tue, Jan 26, 2010 at 1:58 PM, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > That's here.. since I was not sure if it's a best practice or not:
> > http://wiki.xensource.com/xenwiki/XenCommonProblems
> 
> Good point. We need a "standard" criteria on what a "best practice" is :D
> 

Yeah :)

> As far as dedicated dom0 CPU goes, there's this entry from
> http://www.cl.cam.ac.uk/research/srg/netos/xen/readmes/user/user.html
> 
> "If you are running IO intensive tasks, its typically better to
> dedicate either a hyperthread or whole core to running domain 0, and
> hence pin other domains so that they can't use CPU 0. If your workload
> is mostly compute intensive, you may want to pin vcpus such that all
> physical CPU threads are available for guest domains."
> 
> Since in my environment I/O (disk and network) becomes the bottleneck,
> it's a best practice for me.
> 

Well.. I'll add a note of this to XenBestPractices :)

-- Pasi


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