CEPH filesystem development
 help / color / mirror / Atom feed
From: Joao Eduardo Luis <joao.luis@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: less cores more iops / speed
Date: Thu, 08 Nov 2012 00:00:37 +0000	[thread overview]
Message-ID: <509AF625.8040207@inktank.com> (raw)
In-Reply-To: <509ADA6A.9000807@profihost.ag>

On 11/07/2012 10:02 PM, Stefan Priebe wrote:
> Hello again,
> 
> I've noticed something really interesting.
> 
> I get 5000 iops / VM for rand. 4k writes while assigning 4 cores on a
> 2.5 Ghz Xeon.
> 
> When i move this VM to another kvm host with 3.6Ghz i get 8000 iops
> (still 8 cores) when i then LOWER the assigned cores from 8 to 4 i get
> 14.500 iops. If i assign only 2 cores i get 16.000 iops...
> 
> Why does less kvm cores mean more speed?

Totally going on a limb here, but might be related to the cache maybe?
When you have more cores your threads may bounce around the cores and
invalidate cache entries as they go by; will less cores you might end up
with some sort of twisted, forced cpu affinity that allows you to take
advantage of caching.

But I don't know, really. I would be amazed if what I just wrote had an
ounce of truth, and would be completely astonished if that was the cause
for such a sudden increase on iops.

  -Joao

> 
> Greets,
> Stefan
> -- 
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2012-11-08  0:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07 22:02 less cores more iops / speed Stefan Priebe
2012-11-08  0:00 ` Joao Eduardo Luis [this message]
2012-11-08  0:16   ` Openstack - Boot From New Volume Quenten Grasso
2012-11-08  0:59   ` less cores more iops / speed Mark Nelson
2012-11-08  8:45     ` Stefan Priebe - Profihost AG
2012-11-08  8:58       ` Alexandre DERUMIER
2012-11-08  9:02         ` Stefan Priebe - Profihost AG
2012-11-08  9:05           ` Alexandre DERUMIER
2012-11-08  9:28             ` Stefan Priebe - Profihost AG
2012-11-08 13:19       ` Mark Nelson
2012-11-08 15:14         ` Stefan Priebe - Profihost AG
2012-11-08 15:53           ` Alexandre DERUMIER
2012-11-08 21:52             ` Andrey Korolyov
2012-11-09  8:43             ` Stefan Priebe - Profihost AG
2012-11-08  0:59   ` Mark Nelson
2012-11-08  5:42 ` Dietmar Maurer
2012-11-08  5:49   ` Dietmar Maurer
2012-11-08  6:20     ` Stefan Priebe - Profihost AG
2012-11-08  5:49   ` Stefan Priebe - Profihost AG
2012-11-08  5:54     ` Dietmar Maurer
2012-11-08  6:21       ` Stefan Priebe - Profihost AG
  -- strict thread matches above, loose matches on Subject: below --
2012-11-12 15:33 [pve-devel] " Stefan Priebe - Profihost AG
     [not found] ` <50A116DC.2020509-2Lf/h1ldwEHR5kwTpVNS9A@public.gmane.org>
2012-11-12 15:39   ` Alexandre DERUMIER

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=509AF625.8040207@inktank.com \
    --to=joao.luis@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox