Ask Your Question

Revision history [back]

Turn off the container-replicators too, or in fact all the background consistency processes, whittle down to the bone and turn stuff back on one at a time. I think the replication checks on those expiring object containers may be the culprit.

I've never seen a "this hardware gets you these numbers" data set published anywhere. Last summit there was a lot of sessions that talked about HOW to benchmark swift (ssbench, and cosbench from intel, and some other benchmark utility from HP/Mark Seger). I'm hoping this year we'll see more people reporting some numbers out of their configurations so the community can begin to establish some baseline expectations. The swift repo ships with swift-bench, so that's fairly ubiquitous - you may try to get a simple scenario together that exhibits the ChunkReadTimeouts you're seeing.