<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet title="XSL formatting" type="text/xsl" href="http://www.gandibar.net/feed/rss2/xslt" ?><rss version="2.0"
  xmlns:dc="http://purl.org/dc/elements/1.1/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>Gandi Bar - Tag - Hosting trial  - Comments</title>
  <link>http://www.gandibar.net/</link>
  <atom:link href="http://www.gandibar.net/feed/tag/Hosting%20trial/rss2/comments" rel="self" type="application/rss+xml"/>
  <description>Gandi blog, to share our opinions</description>
  <language>en</language>
  <pubDate>Fri, 17 May 2013 22:25:02 -0400</pubDate>
  <copyright></copyright>
  <docs>http://blogs.law.harvard.edu/tech/rss</docs>
  <generator>Dotclear</generator>
  
    
    
    <item>
    <title>Hosting improvements - more, more, more - pascal</title>
    <link>http://www.gandibar.net/post/2009/02/23/Hosting-improvements-more-more-more#c169023</link>
    <guid isPermaLink="false">urn:md5:7b4160bcda37ad3f9b0e1dbb7e3f957b</guid>
    <pubDate>Mon, 02 Mar 2009 14:52:41 +0100</pubDate>
    <dc:creator>pascal</dc:creator>
    
    <description>&lt;p&gt;Hi,&lt;/p&gt;


&lt;p&gt;Yes, driver domain has guaranteed ressources for virtual I/Os.&lt;/p&gt;


&lt;p&gt;Today xen is configured with strict (credit) partitionning, equally important domains.&lt;br /&gt;
You get a fixed amount of credit with each share.&lt;/p&gt;


&lt;p&gt;However, we do not want the share to appear excellent at the beginning (because you're alone on a node, you get full idle cpu for yourself) and degrade over time with no user idea of when it will stabilize. As people can try our servers &amp;quot;for a few minutes&amp;quot;, that would be kind of lying. We want the user to experience an expected, stable performance level.&lt;/p&gt;


&lt;p&gt;So we slightly overcommit on the credit, and as we'll get better at migrating vms accross nodes to achieve a little balance, we'll probably overcommit a little more.&lt;/p&gt;</description>
  </item>
      
    
    <item>
    <title>Hosting improvements - more, more, more - Anonymous</title>
    <link>http://www.gandibar.net/post/2009/02/23/Hosting-improvements-more-more-more#c169020</link>
    <guid isPermaLink="false">urn:md5:4566c676529c9e44ab61bbf90090819a</guid>
    <pubDate>Sun, 01 Mar 2009 20:32:59 +0100</pubDate>
    <dc:creator>Anonymous</dc:creator>
    
    <description>&lt;p&gt;Your data about CPU utilization reminds me of a couple of questions I have about Gandi's hosting service.&lt;/p&gt;


&lt;p&gt;Do you have Xen configured to strictly partition CPU resources and not allow domains to exceed them, or can one domain take more CPU if another domain falls idle?  The latter seems like a better way to ensure that CPUs stay near 100% utilization at all times.&lt;/p&gt;


&lt;p&gt;Also, given how Xen does virtual I/O through domain 0, you should have Xen configured so that domain 0's VCPUs get dedicated physical CPUs which nothing else can run on.  This will significantly improve I/O performance.&lt;/p&gt;</description>
  </item>
      
</channel>
</rss>