lkml.org 
[lkml]   [2008]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Btrfs v0.16 released
> The async worker threads should be spreading the load across CPUs pretty
> well, and even a single CPU could keep up with 100MB/s checksumming.
> But, the async worker threads do randomize the IO somewhat because the
> IO goes from pdflush -> one worker thread per CPU -> submit_bio. So,
> maybe that 3rd thread is more than the drive can handle?

You have more threads with duplication?

>
> btrfsck tells me the total size of the btree is only 20MB larger with
> checksumming on.
>
> > > Btrfs no duplication 76.83 MB/s
> > > Btrfs no dup no csum no inline 76.85 MB/s
> >
> > But without duplication they are basically free here at least
> > in IO rate. Seems odd?
> >
> > Does it compute them twice in the duplication case perhaps?
> >
>
> The duplication happens lower down in the stack, they only get done
> once.

Ok was just speculation. The big difference still seems odd.

-Andi


\
 
 \ /
  Last update: 2008-08-15 03:41    [W:0.067 / U:3.584 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site