On 2016-11-24 12:43, Carlos E. R. wrote:
On 2016-11-24 12:14, Dave Howorth wrote:
On 2016-11-24 02:33, Carlos E. R. wrote:
On 2016-11-19 14:33, Carlos E. R. wrote:
On 2016-11-19 00:05, Greg Freemyer wrote:
I know someone that is an expert on this (it is his job), perhaps he is reading. I'll ping him, just in case ;-)
Well, he no longer reads this list, too busy, but he gave me some ideas, which I'll translate to English here.
First, run away from complexities, the simplest solution can be the best. Don't be led by the bells and whistles you read on internet.
He says he still prefers ZFS because it does CRC of data blocks on disk, so that it ensures that data is properly stored. Also it allows for deduplication. The snag is it uses a lot of RAM.
Just to add a note of caution from my own experience. Our sysadmins like ZFS so when I needed a new data store to replace some old Reiser 3 and XFS ones, they set up a ZFS pool. I tested it and it had absolutely dreadful performance, unusable. They bought some SSDs to add to the pool for the metadata and they upgraded ZFS. It now works acceptably but I don't find it as easy to manage (but maybe that's just lack of familiarity?)
I'm also not familiar myself with ZFS, but my correspondent is. But remember he said that ZFS consumes lots of RAM.
Yes, the server has 64 GB of main memory, so I don't think that was the problem :) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org