<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:coop="http://www.google.com/coop/namespace"
		>
<channel>
	<title>Comentarii la: Partajare CPU in Xen</title>
	<atom:link href="http://www.lamp.ro/virtualizare-xen-openvz/partajare-cpu-in-xen/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.lamp.ro/virtualizare-xen-openvz/partajare-cpu-in-xen/</link>
	<description>Platforma de hosting cu software liber, gratuit, open source.</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:28:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>De către: Sergiu</title>
		<link>http://www.lamp.ro/virtualizare-xen-openvz/partajare-cpu-in-xen/comment-page-1/#comment-2633</link>
		<dc:creator>Sergiu</dc:creator>
		<pubDate>Wed, 16 Dec 2009 11:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.lamp.ro/?p=205#comment-2633</guid>
		<description>Ai dreptate. Merci de completare :)</description>
		<content:encoded><![CDATA[<p>Ai dreptate. Merci de completare <img src='http://www.lamp.ro/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>De către: Lucian</title>
		<link>http://www.lamp.ro/virtualizare-xen-openvz/partajare-cpu-in-xen/comment-page-1/#comment-2630</link>
		<dc:creator>Lucian</dc:creator>
		<pubDate>Tue, 15 Dec 2009 17:43:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.lamp.ro/?p=205#comment-2630</guid>
		<description>&lt;blockquote&gt;Astfel daca avem un sistem virtual care are setat “cpu_cap=30“, sistemul nu va putea sa consume mai mult de 30% din puterea de calcul a procesorului sau a procesoarelor, dupa caz.&lt;/blockquote&gt;

Citeste cu atentie http://wiki.xensource.com/xenwiki/CreditScheduler :

&lt;blockquote&gt;The cap optionally fixes the maximum amount of CPU a domain will be able to consume, even if the host system has idle CPU cycles. The cap is expressed in percentage of one physical CPU: 100 is 1 physical CPU, 50 is half a CPU, 400 is 4 CPUs, etc... The default, 0, means there is no upper cap.&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<blockquote><p>Astfel daca avem un sistem virtual care are setat “cpu_cap=30“, sistemul nu va putea sa consume mai mult de 30% din puterea de calcul a procesorului sau a procesoarelor, dupa caz.</p></blockquote>
<p>Citeste cu atentie <a href="http://wiki.xensource.com/xenwiki/CreditScheduler">http://wiki.xensource.com/xenwiki/CreditScheduler</a> :</p>
<blockquote><p>The cap optionally fixes the maximum amount of CPU a domain will be able to consume, even if the host system has idle CPU cycles. The cap is expressed in percentage of one physical CPU: 100 is 1 physical CPU, 50 is half a CPU, 400 is 4 CPUs, etc&#8230; The default, 0, means there is no upper cap.</p></blockquote>
]]></content:encoded>
	</item>
</channel>
</rss>

