Yes, I think you should try with crc enabled as it is recommended for network
level corruption detection.
It will definitely add some cpu cost but it is ~5x lower with Intel new cpu
instruction set..
-Original Message-
From: Stefan Priebe - Profihost AG [mailto:s.pri...@profihost.ag]
Se
nath Roy ; ceph-users@lists.ceph.com
> Subject: Re: [ceph-users] optimized SSD settings for hammer
>
>
> Am 25.01.2016 um 08:54 schrieb Somnath Roy:
> > ms_nocrc options is changed to the following in Hammer..
> >
> > ms_crc_data = false
> > ms_crc_h
Am 25.01.2016 um 08:54 schrieb Somnath Roy:
> ms_nocrc options is changed to the following in Hammer..
>
> ms_crc_data = false
> ms_crc_header = false
If i add those the osds / client can't comunicate any longer.
> Rest looks good , you need to tweak the shard/thread based on yo
ms_nocrc options is changed to the following in Hammer..
ms_crc_data = false
ms_crc_header = false
Rest looks good , you need to tweak the shard/thread based on your cpu complex
and total number of OSDs running on a box..
BTW, with latest Intel instruction sets crc overhead is re
Hi,
is there a guide or recommendation to optimized SSD settings for hammer?
We have:
CPU E5-1650 v3 @ 3.50GHz (12 core incl. HT)
10x SSD / Node journal and fs on the same ssd
currently we're runnig:
- with auth disabled
- all debug settings to 0
and
ms_nocrc = true
osd_op_num_threads_per_shar
