4 ms·
> If we do a full pod swap for a blank, we are disk / CPU limited in the rebuild, not 10 Gbit/sec limited Wow. This is pretty shocking TBH. My basic ceph nodes
by scurvy 11y ago
> If we do a full pod swap for a blank, we are disk / CPU limited in the rebuild, not 10 Gbit/sec limited
Wow. This is pretty shocking TBH. My basic ceph nodes will crush a 40gbps link doing a rebuild/rebalance. What's your bottleneck?
- mappu 11y agoBackblaze use an in-house Java pseudo-RAID layer based on Reed-Solomon codes, with 17 data shards and 3 parity shards. There are some performance numbers here https://www.backblaze.com/blog/reed-solomon/ https://www.backblaze.com/blog/reed-solomon/ (2015).
- nwmcsween 11y agoI wouldn't mind understanding why, I'm assuming at the time ceph wasn't mature enough (and still somewhat is due to btrfs, yes I know it's optional).
- scurvy 11y agobtrfs isn't a requirement nor really a recommendation for production ceph clusters. It was really only there for weirdo benchers. Bluestore and rocks DB really changes the back-end story altogether. No more POSIX filesystem junk with journals and such.