All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: "Sidorov, Andrei" <Andrei.Sidorov@arrisi.com>
Cc: Dave Chinner <david@fromorbit.com>, Ryan Lortie <desrt@desrt.ca>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: ext4 file replace guarantees
Date: Sat, 22 Jun 2013 10:06:13 -0400	[thread overview]
Message-ID: <20130622140613.GE4727@thunk.org> (raw)
In-Reply-To: <C0F0BC787567C848B2C90989451123DA2363CBBE@ATLEXMBX4.ARRS.ARRISI.com>

On Sat, Jun 22, 2013 at 01:40:26PM +0000, Sidorov, Andrei wrote:
> Me too, but people have to do that because fs api is too generic and
> at the same time one has to account fs specifics in order to make
> their app take most advantage or at least to avoid inefficiencies.
> For example I have an app that constantly does appending writes to
> about 15 files and I must ensure that no more than 5 seconds will be
> lost in an event of system crash or power loss.

Stop right there.  If you are doing lots of appending writes, and you
dont want to lose no more than 5 seconds, why do you have 15 files?
Why send your appending writes into a single file and then later on,
disaggregate out the logs when you need to read them?  With 15 files,
no matter what you are doing, you will be forcing the heads to seek
all over the place, and since the 4k blocks won't be full when you
sync them, you're wasting write cycles and disk bandwidth.

See what I mean?  There's a reason why I said the fault was
incompetent application design, not just incomplement implementation.

	    			    	 	      - Ted

  reply	other threads:[~2013-06-22 14:06 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 21:34 ext4 file replace guarantees Ryan Lortie
2013-06-21  0:59 ` Theodore Ts'o
2013-06-21 12:43   ` Ryan Lortie
2013-06-21 13:15     ` Theodore Ts'o
2013-06-21 13:51       ` Ryan Lortie
2013-06-21 14:33         ` Theodore Ts'o
2013-06-21 15:24           ` Ryan Lortie
2013-06-21 20:35             ` Theodore Ts'o
2013-06-22  3:29               ` Dave Chinner
2013-06-22  4:47                 ` Theodore Ts'o
2013-06-22 13:40                   ` Sidorov, Andrei
2013-06-22 14:06                     ` Theodore Ts'o [this message]
2013-06-22 14:41                       ` Sidorov, Andrei
2013-06-23  1:58                   ` Dave Chinner
2013-06-21 16:25         ` Joseph D. Wagner
2013-06-21 21:05           ` Theodore Ts'o
2013-06-21 21:49             ` Sidorov, Andrei
2013-06-22 12:56               ` Theodore Ts'o
2013-06-22 14:01                 ` Sidorov, Andrei
2013-06-22 14:30                   ` Theodore Ts'o

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=20130622140613.GE4727@thunk.org \
    --to=tytso@mit.edu \
    --cc=Andrei.Sidorov@arrisi.com \
    --cc=david@fromorbit.com \
    --cc=desrt@desrt.ca \
    --cc=linux-ext4@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 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.