Return-Path: X-Original-To: apmail-cloudstack-users-archive@www.apache.org Delivered-To: apmail-cloudstack-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 91B801752F for ; Wed, 1 Apr 2015 15:54:13 +0000 (UTC) Received: (qmail 93889 invoked by uid 500); 1 Apr 2015 15:54:06 -0000 Delivered-To: apmail-cloudstack-users-archive@cloudstack.apache.org Received: (qmail 93845 invoked by uid 500); 1 Apr 2015 15:54:06 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 93833 invoked by uid 99); 1 Apr 2015 15:54:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2015 15:54:06 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of aemneina@gmail.com designates 209.85.212.174 as permitted sender) Received: from [209.85.212.174] (HELO mail-wi0-f174.google.com) (209.85.212.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2015 15:54:01 +0000 Received: by wiaa2 with SMTP id a2so71983736wia.0 for ; Wed, 01 Apr 2015 08:51:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=2JqX6iQunTuayHID+iQ6ndmD+go2joaLYMnBnnUT6uE=; b=kLAKpSMaHhh9PIdcywAvjFJ4XWBBGDM+0kLa1K3NN+KeILpQRTIgbQ18VNKRkyjqoX YHUg/6Zrk2bvHW5FJc1NqrLIY1sfSZLxnVxMLjBLr+RFZboYcQmM967MGQ49ozJoFyPW SmMJG1fVtUWPfYCGB0YUYfuw50bGibBodpUdyRmHe07Mue/HdB9b4xDaS03UtsNqyBuu K2FhGp7NkFkf2Y+tP3gLcLBqmnIHTXD9N4zT8xyCussl5Ye9+4PWBoiWboQEFt/Re8+o bcD1+VlXD2cvojci1A+PR3mtbtUwLSHqyvce5/qZg3pKZpAbY58rtMQLb36wPUTna/6i T5Dw== X-Received: by 10.194.193.99 with SMTP id hn3mr86130797wjc.148.1427903486046; Wed, 01 Apr 2015 08:51:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.39.225 with HTTP; Wed, 1 Apr 2015 08:51:05 -0700 (PDT) Reply-To: aemneina@gmail.com In-Reply-To: <550C3D2D.9090802@vertigs.lv> References: <550C3D2D.9090802@vertigs.lv> From: Ahmad Emneina Date: Wed, 1 Apr 2015 08:51:05 -0700 Message-ID: Subject: Re: About CPU usage To: Cloudstack users mailing list Content-Type: multipart/alternative; boundary=047d7b874e5e0f37730512abb08a X-Virus-Checked: Checked by ClamAV on apache.org --047d7b874e5e0f37730512abb08a Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable you might want to try this query on the dev mailing list, they could have more insight into the artificial limit of 4. My guess is thats a poorly worded recommendation. On Fri, Mar 20, 2015 at 8:30 AM, M=C4=81rti=C5=86=C5=A1 Jakubovi=C4=8Ds wrote: > Hello, > > In my demo server with XenServer 6.2 I got quad core CPU with > hyperthreading (8 vCPU total). In cluster I am able to use > cpu.overprovisioning.factor 5.0 and more. Why so, if in documentation > described maximum over-provisioning can't be bigger than 4? > http://docs.cloudstack.apache.org/projects/cloudstack- > administration/en/4.3/hosts.html#limitations-on-over- > provisioning-in-xenserver-and-kvm > > Also, looks like is possible to trick CPU over-provisioning by entering > less CPU speed in Compute Offering than are really in server. > > Maybe someone can share they experience about CPU over-provisioning with > XenServer? > > Thanks. > --047d7b874e5e0f37730512abb08a--