linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Oliver Rath <rath@mglug.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] howto speed-up thinpool-devices?
Date: Sat, 24 Aug 2013 10:42:37 +0200	[thread overview]
Message-ID: <521871FD.8000700@mglug.de> (raw)

Hi list,

Im using thinpool-devices (and snapshots, too). I know, thinpool-devices
arent the fastest one, but maybe there could make more use of read (and
maybe write) caching. In my test-system are 32GB of ram, but there is a
max use of cache about <1GB, not more, by heavily use of these devices.

Is it possible to speed up the reading with growing up the cache use?
The /sys/block/dm-X/.. directories have lots of parameters, but Im not
experienced for that. Maybe Im looking@the wrong place and modifying
kernel parameters (scheduler etc.) are the better way?

Tfh!
Oliver

             reply	other threads:[~2013-08-24  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-24  8:42 Oliver Rath [this message]
2013-09-03 10:06 ` [linux-lvm] howto speed-up thinpool-devices? Marian Csontos
2013-09-28 20:42   ` [linux-lvm] buffers shared between different devs? (was: howto speed-up thinpool-devices?) Linda A. Walsh
2013-09-03 10:54 ` [linux-lvm] howto speed-up thinpool-devices? Zdenek Kabelac

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=521871FD.8000700@mglug.de \
    --to=rath@mglug.de \
    --cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).