CEPH filesystem development
 help / color / mirror / Atom feed
From: Stefan Kleijkers <stefan@unilogicnetworks.net>
To: Madhusudhana U <madhusudhana.u.acharya@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: SAS disks for OSD's
Date: Mon, 23 Apr 2012 21:22:15 +0200	[thread overview]
Message-ID: <4F95ABE7.6020202@unilogicnetworks.net> (raw)
In-Reply-To: <loom.20120423T175101-19@post.gmane.org>

Hello,

I don't think you will see a great difference in performance between 
"sas" and "sata" disks, because the connection type is only a minor 
point in performance. There are other factors that impact the 
performance a lot more.
How many RPMs are the disks? The more RPM the lower the average seek 
time. Lower average seek time is great for random IO.
How dense are the disks, with more sectors per cilinder you can read or 
write more data per round. Great for sequential IO.

And there are other factors that impact performance. But in general the 
"sata" disks are disks with low RPMs and high density, therefor they are 
(in general) poor on random IO and great on sequential IO. With the 
"sas" disks it's the other way around. But even something like 2.5" vs 
3.5" can impact performance because it can have impact on the density of 
the disk.

But I think using a "sas" disk as journal won't give you any performance 
gain. As journal you want a device that can handle a lot of IOPS and 
also have a lot of bandwidth.
I think a SSD gives a good balance between IOPS, bandwidth, size and 
price (compared to sata/sas disks and nvram).

"sas" disks for the OSD can gain you performance compared to the "sata" 
disks, but it depends on the specs of the disk, the workload, the kind 
and size of the journal, ratio between write/read, etc. So it's a little 
difficult to tell you if the "sas" disks gain you any or enough 
performance for the extra cost.

Stefan

On 04/23/2012 05:56 PM, Madhusudhana U wrote:
> Hi all,
> Is any performance benefit we will get using SAS storage for OSD instead of
> SATA storage ? Is any one using SAS drives which is producing good performance?
>
> Or I can use SAS drives for journal and SATA storage for OSD?
>
> Which one in above two scenario would yield a better performance?
>
> I would like to test above scenarios, before i would like to hear if
> anyone got good results with SAS drives.
>
> Thanks
> __M
>
> --
> 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-04-23 19:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 15:56 SAS disks for OSD's Madhusudhana U
2012-04-23 19:22 ` Stefan Kleijkers [this message]

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=4F95ABE7.6020202@unilogicnetworks.net \
    --to=stefan@unilogicnetworks.net \
    --cc=ceph-devel@vger.kernel.org \
    --cc=madhusudhana.u.acharya@gmail.com \
    /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