big flash disks?
joern at logfs.org
Wed Jun 4 02:25:57 EDT 2008
On Tue, 3 June 2008 19:44:29 +0100, Jamie Lokier wrote:
> But he quites a high write IOP rate, which is sometimes taken to mean
> a high rate of database commits (e.g. fsync). That can't be done with
> eraseblock-sized writes.
I don't remember reading the words 'commit' or 'sync' in any of his
> If it's not high commit rate, then the quoted IOP rate is misleading
> because you can do the same reordering thing with hard disks to get a
> high write rate. (Albeit hard disks suffer from random reads more if
> ordering writes disorders reads).
> If you think it's just reordering, not committing each 4k write one
> after the other quickly, I'll ask him about it.
At least on some of the cheaper SSDs I believe the only way to commit a
write is by writing the whole eraseblock. And if you don't explicitly
request that, the SSD will do it for you. Either way you take the
Alternatively he could walk up the tree for commits and store all higher
layers in the same eraseblock. 16k would be enough for a commit on
disks up to 512G in size, 20k up to 256T. On real flash that simply
won't fly, as GC will cause a deadlock sooner or later. With an SSD you
can still get away with it, as 4k writes without erases are slow, but at
Sometimes, asking the right question is already the answer.
More information about the linux-mtd