search

open-city / recycling

Crowdsourcing data about which residential buildings do not have recycling in Chicago
MIT License
27 stars 24 forks source link

Logentries: Memory Quota Exceeded #144

Closed matiaskitty closed 8 years ago

matiaskitty commented 8 years ago

Now the LogEntries alerts are continually coming in. According to the LogEntries dashboard this issue is Critical.

screen shot 2015-10-14 at 9 36 45 pm

evz commented 8 years ago

@matiaskitty Wow, I'd be honored to help out here but I'm not sure I have access to that app. if this wasn't assigned to me accidentally, just point me in the right direction and I'll see what I can figure out.

benwilhelm commented 8 years ago

@alexkahn, do you have a minute to look at this? The app is using more memory than the heroku dyno allows and is starting to swap.

https://devcenter.heroku.com/articles/error-codes#r14-memory-quota-exceeded

Not the end of the world for the moment as long as we're not expecting a traffic spike. My first though would be that serializing the entire map's result set to save or retrieve it from memcached is causing the overage. I don't think I'll have time to troubleshoot this till the weekend. It might just mean upping to a paid dyno, but we probably want to start returning the results in smaller sets regardless.

alexkahn commented 8 years ago

I cranked up the app by adding a small cluster implementation for adding multiple processes. We did actually bump up to a paid (hobby) dyno but I think it might be a good idea to either upgrade again (for more memory) or off-load the static assets to a CDN or similar.

alexkahn commented 8 years ago

@evz We would love to have you - feel free to submit a Pull Request any time. I don't think this was an intentional assignment but if you've got some Node.js or client side JavaScript chops, feel free to make a contribution!