rubyforgood
Heroku: Memory leak / overload on flaredown-api dynos
Logan thinks this is related to a memory leak of some sort. More details to follow.
@samanthar8 Who is working on this?
@compwron @lmerriam had mentioned on our call that there were some production metrics available which demonstrated some sort of memory exhaustion issue or similar. Can we get more detail on that in order to determine appropriate fixes?
Also, this is a duplicate of https://github.com/rubyforgood/Flaredown/issues/480 no?
I've added @benlangfeld and @bklang to the Heroku account. The memory issue shows up on the flaredown-api dynos specifically. Please let me know if I should add others to the account.
Thanks @lmerriam . I'll close this as a duplicate and look into it in #480
@benlangfeld @samanthar8 we may want to track the memory overload as an issue separate from the problem with the chat/discussion, since I am not 100% sure they cause each other.
It looks like we have a solution for the broken chat feature, if that doesn't solve the memory problem then I wouldn't want to lose track of it.