Geek asks and answers

Error R14 (memory quota exceeded) Does not appear in the new relic

Continue to receive the error R14 (memory quota exceeded) on Heroku.

Memory profiling in django application locally I don't see any problems. We installed a new relic, and everything looks fine there, with the exception of one oddity:

http://screencast.com/t/Uv1W3bjd

Memory usage varies around 15 mb per dino, but for some reason the “dynos running” thing quickly scales to 10+. Not sure how this makes sense, as we currently only work on web dino.

We also work with celery, and it looks like it looks fine there too (about 15 mb). Although this is suspicious, because I believe that an error occurred while starting this problem.

Some of our queries take some time, because they execute a soap request for an echo, which can take from 6 to 10 seconds. Does it somehow block and cause a reversal of the new speaker?

Here is my proc file:

web: python manage.py collectstatic --noinput; python manage.py compress; newrelic-admin run-program python manage.py run_gunicorn -b "0.0.0.0:$PORT" -w 9 -k gevent --max-requests 250
celeryd: newrelic-admin run-program python manage.py celeryd -E -B --loglevel=INFO

The main problem is a memory error.

+5
source share
1 answer

I BELIEVE I might have found a problem.

Based on reports such as these , I thought that I should be located somewhere in the region of 9-10 gunsmith workers. I believe this is wrong (or at least for the work performed by my application).

I worked with 9 gunsmith workers and finally realized that this is the only real difference between the heroic and the local (as far as the configuration is concerned).

In accordance with

+13
source

More articles:


All Articles