> -----Original Message----- > From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel- > owner@xxxxxxxxxxxxxxx] On Behalf Of Curley, Matthew > Sent: Thursday, October 01, 2015 5:33 PM > > We've been trying to reproduce the allocator performance impact on 4K > random reads seen in the Hackathon (and more recent tests). At this point > though, we're not seeing any significant difference between tcmalloc and > jemalloc so we're looking for thoughts on what we're doing wrong. Or at > least some suggestions to try out. > > More detail here: > https://drive.google.com/file/d/0B2kp18maR7axTmU5WG9WclNKQlU/view? > usp=sharing > > Thanks for any input! This problem is more obvious on writes than reads (I noticed that CPU usage on writes is way more erratic than on reads, where it's pretty much constant), also - more clients would be better (or worse, depending on how you look at it). And finally, this gets more serious with time, once tcmalloc caches get filled, it starts to slow down. With best regards / Pozdrawiam Piotr Dałek -- 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
