From: Matthias Schniedermeyer <ms@citd.de>
To: Daire Byrne <daire.byrne@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Contiguous file sequences
Date: Wed, 22 Sep 2010 22:50:52 +0200 [thread overview]
Message-ID: <20100922205052.GA32059@citd.de> (raw)
In-Reply-To: <AANLkTikHqjvEGJb0XnNy+nz7+nHLVLwjF_wp5RZdk_1-@mail.gmail.com>
On 22.09.2010 12:01, Daire Byrne wrote:
> Hi,
....
There is actually a VERY easy solution nowadays. SSD(s)
It doesn't matter if files are continuous or not, SSDs don't care (at
least the better ones)
If you care about "worst case" write performance, zap the whole thing
before usage (a.k.a.: trim) and write in chunks that are sized and
aligned to erase-blocks (or just write in big chunks like 1MB or more).
That should be more or less be enough to prevent latency spikes, that
CAN plague SSDs.
What exactly you need obviously depends on the usual factors:
Needed sustained read/write bandwith, size, money, etc. etc.
Bis denn
--
Real Programmers consider "what you see is what you get" to be just as
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated,
cryptic, powerful, unforgiving, dangerous.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-09-22 20:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 11:01 Contiguous file sequences Daire Byrne
2010-09-22 20:10 ` Eric Sandeen
2010-09-24 10:43 ` Daire Byrne
2010-09-27 4:08 ` Eric Sandeen
2010-09-27 16:30 ` Daire Byrne
2010-09-27 18:35 ` Matthias Schniedermeyer
2010-09-28 1:16 ` Dave Chinner
2010-09-27 20:56 ` Roger Willcocks
2010-09-25 9:42 ` Michael Monnerie
2010-09-22 20:50 ` Matthias Schniedermeyer [this message]
2010-09-22 22:36 ` Dave Chinner
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=20100922205052.GA32059@citd.de \
--to=ms@citd.de \
--cc=daire.byrne@gmail.com \
--cc=xfs@oss.sgi.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