3 ms·
What about potential customers? I've been evaluating your platform and just be completely frustrated with 3 days wasted trying to solve these performance issues
by natmaster 14y ago
What about potential customers? I've been evaluating your platform and just be completely frustrated with 3 days wasted trying to solve these performance issues.
I'm using gunicorn with python, and if I use the sync worker the request queue easily hits 10 seconds and nothing works; if I switch to gevent or eventlet, new-relic tells me that redis is taking the same time stuck getting a value. This is using the same code in my current provider that works just fine with eventlet and scales well.
To add insult to injury, adding dynos actually degrades performance.
- adamwiggins 14y agoThat sucks. It may or may not be related to how the router works, but it's definitely about performance and visibility, which is what this is all about. Can you email me at adam at heroku dot com and I'll connect you with one of our Python experts? I can't promise we'll solve it, but I'd like to take a look.
- nantes 14y agoI'd be really interested to see some public information resulting from debugging Python apps. We're holding pretty steady, but see a fairly constant stream of timeouts due, apparently, to variance in response times. To be sure, we're working on that. But, in the meantime, our experiments with gevent and Heroku have been less than inspiring.
- adamwiggins 14y agoI've connected Nathaniel (poster above) with one of our Python folks. Looking forward to seeing what they discover. Would you be willing to pair up with one of our developers on your app's performance? If so email me (adam at heroku dot com).
- thruflo 14y agoI'm an existing customer using python with gunicorn. I'd be very keen to see any learnings about an optimal setup. Fwiw, I've found the addon / db connection limits to be the primary blocker when load testing so far.