[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Xrenstore and many save/restore cycles...

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
  • Date: Wed, 9 May 2007 18:09:14 +0200
  • Delivery-date: Wed, 09 May 2007 09:07:56 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AceSVGM8Av6YvsIhQ7y1ndlgAxjWAw==
  • Thread-topic: Xrenstore and many save/restore cycles...

Let me first say that I have very little understanding of xenstore, as
it's not an area of Xen that I normally work in. If I've completely
missed something, please let me know.

I've been running a script over the (extended) weekend which saves and
restores HVM domains. In this case, two different domains. 

At this moment in time (around 6000 save/restore operations total),
xenstored is using about 900MB of memory (which is a bit excessive on my
256MB Dom0). Thrashing of the swap is consuming enough time that my
machine is unable to cope with running the domains satisfactorily at
this time. 

Using xenstored-list, I see hundreds (so far) of instance information of
"old" domains that have been killed when being saved, and created with a
new ID when restored. So I've got (I'm guessing) some 6000 or so domains
stored in xenstore. 

Is this something intended, and if so, would [I'm asking because I
haven't tried it] the same effect be expected if 6000 domains where
created and destroyed? If so, what is the purpose of keeping information
about a domain that is no longer there?

I can certainly see problems with servers that for one reason or another
save/restore several domains daily - after a few months, there will be
LOTS of data in the xenstore and potential swap-thrashin causing
problems, or what???


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.