From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Daniel P. Berrange" Subject: Re: VM start time slows with large number of VMs Date: Thu, 6 Sep 2007 18:44:14 +0100 Message-ID: <20070906174414.GH1291@redhat.com> References: <46e038f5.2805420a.2d00.ffff8dd0@mx.google.com> Reply-To: "Daniel P. Berrange" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com, Mats Petersson , "Carb, Brian A" List-Id: xen-devel@lists.xenproject.org On Thu, Sep 06, 2007 at 06:31:28PM +0100, Keir Fraser wrote: > On 6/9/07 18:29, "Mats Petersson" wrote: > > >> If I save the output from the xenstore-ls, the file has 61,318 lines > >> with information from all the VMs run yesterday. I conclude that > >> xenstore does not get cleared on startup. Is there a way to clear it? > > > > > > It is perfectly fine to remove the xenstore.tdb [filename from > > memory] in /var/xen/lib [again, from memory]. Unless of course you > > actually NEED some of your old Xenstrore entries for soemthing, but > > in general, they are fine to be removed completely. > > Yes, actually this would be something perhaps we should do from the xend > startup script, if we can determine that xenstored is not running. It'd be > nice to get a patch. Or just put the database on /dev/shm so its in RAM - that way it just goes away whenever you reboot & you reduce the disk I/O overhead xenstored has. IIRC last time I tested it doubled xenstored performance using /dev/shm Dan -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|