I had a similar issue with my Django project on Heroku. My site performance went down once I enabled memcache, almost entirely due to latency (going up to 100ms at times). This is one of the reasons why I ended up moving off of Heroku and onto an EC2 instance: now I have full control of my stack, I can run what I want locally on the server, and I'm getting much better performance (nginx+gunicorn+memcached+django+johnnycache+rds)
I'm not affiliated with the OP. I maintain my own stack on EC2 due to very specific application requirements. However, something is suspicious if the latency goes up so much due to Memcache alone.
Comments
I had a similar issue with my Django project on Heroku. My site performance went down once I enabled memcache, almost entirely due to latency (going up to 100ms at times). This is one of the reasons why I ended up moving off of Heroku and onto an EC2 instance: now I have full control of my stack, I can run what I want locally on the server, and I'm getting much better performance (nginx+gunicorn+memcached+django+johnnycache+rds)
I'm not affiliated with the OP. I maintain my own stack on EC2 due to very specific application requirements. However, something is suspicious if the latency goes up so much due to Memcache alone.