On Mon, Feb 17, 2014 at 03:20:58AM +0000, Duncan wrote:
> Chris Murphy posted on Sun, 16 Feb 2014 12:54:44 -0700 as excerpted:
> > Also, 10 hours to balance two disks at 2.3TB seems like a long time. I'm
> > not sure if that's expected.
>
> FWIW, I think you may not realize how big 2.3 TiB is, and/or how slow
> spinning rust can be when dealing with TiBs of potentially fragmented
> data...
>
> 2.3TiB * 1024GiB/TiB * 1024 MiB/GiB / 10 hours / 60 min/hr / 60 sec/min =
>
> 66.99... real close to 67 MiB/sec
>
> Since it's multiple TiB we're talking and only two devices, that's almost
> certainly spinning rust, not SSD, and on spinning rust, 67 MiB/sec really
> isn't /that/ bad, especially if the filesystem wasn't new and had been
> reasonably used, thus likely had some fragmentation to deal with.
Don't forget that that is 67MiB/s reading data and 67MiB/s writing
data giving a total of 134MiB/s.
Still, on a good system each disk should have about that speed so it's
about 50% of theoretical maximum. Which is quite good given that the
disks will need to seek between every read and write. In comparison
moving data with LVM gets only about half that speed and that doesn't
even have the overhead of a filesystem to deal with.
MfG
Goswin
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
