linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stan Hoeppner <stan@hardwarefreak.com>
To: linux-bcache@vger.kernel.org
Subject: tuning for mixed rate 800 stream write application
Date: Fri, 03 Oct 2014 21:22:52 -0500	[thread overview]
Message-ID: <542F59FC.1080806@hardwarefreak.com> (raw)

Hello fellow bcache users/developers,

A couple of questions.

1.  How do I disable write caching?
2.  How do I increase the sequential IO tracking window from 128 IOs to say 4096 IOs or nmore?

Our application does small random reads and data is never read twice, so we don't want any read caching.  Reads comprise less than 20% of the IO workload.  It writes ~800 streams to hundreds of preallocated files in parallel using O_DIRECT and AIO.  The stream rates vary from ~50MB/s to less than 2KB/s.  bcache currently seems to be writing a lot of data to cache that should be going directly to the two RAID LUNs, bcache0 and bcache1.  These each show over 150GB cache used or 300GB total of a 400GB SSD, with only 10GB bypassed.  It seems to be writing sequential IO to cache because it's unable to properly classify it due to the small 128 entry tracking window.  Thus throughput is actually about 20 lower than direct to LUN.  It seems clear bcache isn't doing the right thing with classificat
 ion due to the large number of mixed sequential/random IOs in flight.

The boxes have 32 cores and 256GB of RAM so we have plenty of horsepower and memory to dedicate to bcache use.  These boxes are totally IO bound with little CPU/memory use.

Please advise.

Thanks,
Stan

             reply	other threads:[~2014-10-04  2:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04  2:22 Stan Hoeppner [this message]
2014-10-04 19:30 ` tuning for mixed rate 800 stream write application Kai Krakow
2014-10-06  0:10 ` Stan Hoeppner

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=542F59FC.1080806@hardwarefreak.com \
    --to=stan@hardwarefreak.com \
    --cc=linux-bcache@vger.kernel.org \
    /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).