AFAIR I observed the issue for tcmalloc as well. There is a
corresponding note in the ticket..
On 30.06.2017 0:32, Mohamad Gebai wrote:
On 06/29/2017 05:18 PM, Sage Weil wrote:
On Thu, 29 Jun 2017, Mohamad Gebai wrote:
Also, preloading libtcmalloc makes this behavior disappear (at least for
this program), which confirms further the hypothesis, since tcmalloc
does larger allocations internally.
What do you mean by that last paragraph? We should be linking against
tcmalloc in ceph. But you see that using tcmalloc avoids the problem in
the reproducer?
Yes, that's exactly it. That's why I'm asking about the pattern usage,
so I can try to reproduce it in Ceph. I'll try fio as you suggested and
follow up. If you have any thoughts in the mean time, please let me know.
Mohamad
--
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
