All of lore.kernel.org
 help / color / mirror / Atom feed
From: "João Eduardo Luís" <jecluis@gmail.com>
To: madhusudhana <madhusudhana.u.acharya@gmail.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: TOO SLOW data write speed and delete.. NEED HELP
Date: Tue, 13 Mar 2012 19:33:40 +0000	[thread overview]
Message-ID: <4F5FA114.7070806@gmail.com> (raw)
In-Reply-To: <loom.20120313T113524-750@post.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

On 03/13/2012 10:39 AM, madhusudhana wrote:
> Hi all,
> Can someone PLEASE help me to understand why data copying (simple cp
> or rsync) is SO slow in CEPH ? And delete command (\rm -rf) for removing
> a small (175M) directory is taking so much of time. Because of this,
> i am not able to complete evaluation of ceph using my actual workload. 
> 
> I am hereby requesting all to help me in finding out the reason for 
> slow write/delete in my ceph cluster. I am really trying hard to 
> complete the evaluation with actual workload but not able to copy the
> data whats required for evaluation to ceph cluster bcz of slow copy.
> 
> I really appreciate any help on this.
> 
> Thanks in advance
> Madhusudhan
> 

Hi Madhusudhan,

Are you using Btrfs? And are you taking snapshots while you're
performing those operations?

-- 
João Eduardo Luís
gpg key: 477C26E5 from pool.keyserver.eu


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]

  reply	other threads:[~2012-03-13 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 10:39 TOO SLOW data write speed and delete.. NEED HELP madhusudhana
2012-03-13 19:33 ` João Eduardo Luís [this message]
2012-03-14  4:28   ` madhusudhana
2012-03-14 11:42     ` João Eduardo Luís
2012-03-14 17:05       ` madhusudhana
2012-03-14 17:42         ` João Eduardo Luís
2012-03-14 17:56     ` Sage Weil
2012-03-15  7:34       ` madhusudhana

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=4F5FA114.7070806@gmail.com \
    --to=jecluis@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.