Originally posted by Hauldren Collider
View Post
My company launched a python-powered extremely dynamic website (Plone is the CMS), and immediately after putting it in production the site slowed to a CRAWL. It was HIDEOUSLY slow. Patheticly slow. Unbelievably slow.
I had to "fix" the problem by implementing aggressive HTTP proxy caches (Varnish), hand-tuning browser cache settings, implementing memcached (which was a MySQL perf problem more than Python), and basically get the code to run once, cache for hours...and never run again. Because it was so ****ing slow.
Even that didn't fix it. I had to break it up into an Amazon EC2 array with a load balancer. It'd constantly poll the load levels on the server, and once it sustained at a high level it'd automatically spawn a new server (boots, configs, and installs in ~3 mins) and attaches to the load balancer to handle the extra load. During our lunch time peak traffic, the site runs on 12 ****ing servers...it shrinks down to 1 automatically at its lowest traffic (3am).
Anyway...that was a ****ing month of a nightmare, all thanks to Python.
Comment