Thanks Mark ! I got my old numbers back for 16K min_alloc_size , yet to try with 4K min_alloc_size. Here is the perf trace I was talking in the standup.. 3.63% libtcmalloc.so.4.2.6 [.] tc_newarray 2.39% libtcmalloc.so.4.2.6 [.] tc_deletearray 2.22% libc-2.23.so [.] __memcpy_sse2_unaligned 1.69% ceph-osd [.] _ZN7rocksdb6crc32c10ExtendImplIXadL_ZNS0_L10Slow_CRC32EPmPPKhEEEEjjPKcm See the last one , it is using Slow_CRC still , but with much lower cpu utilization now than the previous master. Igor/Mark, Could you please confirm you are also seeing the same ? Thanks & Regards Somnath -----Original Message----- From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of Igor Fedotov Sent: Thursday, November 03, 2016 9:02 AM To: Mark Nelson; ceph-devel Subject: Re: rocksdb optimization regression (bluestore perf regression) Mark, thanks for update. I've Just made a brief try. Performance is much better now but numbers I can see with my old branch are still unreachable. Approx х2 times slower ( it was ~10х slower before) for random 4K r/w using FIO against standalone bluestore instance. Thanks, Igor On 03.11.2016 17:59, Mark Nelson wrote: > Mostly this is for Igor and Somnath: > > It looks like the regression was indeed caused by lack of O2 > optimization for rocksdb in master after 418bfd7. The following PR > appears to resolve the performance regression in my tests: > > https://github.com/ceph/ceph/pull/11767 > > Mark > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies). ��.n��������+%������w��{.n����z��u���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
