Comment 6 for bug 1595916

well, that pipeline and proxy configuration look pretty reasonable to me.

You could reduce the workers to 1, same thing for the account/container/object services - but that's still no excuse for any individual worker bloating beyond some megabytes... I monitor RSS by process group on some production swift deployments and all of the dozens of proxy workers combined seem to hang around ~250MB, which is a lot... but a far cry from 60-80GiB?

Also in all observed cases the object-server workers are much larger than the proxy-servers workers...

I don't really have any other immediate hypothesis? I can't really think of what else might be interesting to try and capture on this system? netstat? lsof? swift-ring-builder output?

"I restarted swift-proxy and after 30 minutes its back using 63GB"

^ maybe it'd be possible to get on a sandbox environment with this configuration and observe that directly? Not sure what'd I'd dig around for exactly - short of instrumenting with heapy ;)