search

rubyforgood / Flaredown

Flaredown web app and API
http://www.flaredown.com
GNU General Public License v3.0
39 stars 15 forks source link

Heroku: Memory leak / overload on flaredown-api dynos #497

Open samanthar8 opened 2 years ago

samanthar8 commented 2 years ago

Logan thinks this is related to a memory leak of some sort. More details to follow.

benlangfeld commented 2 years ago

@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?

benlangfeld commented 2 years ago

Also, this is a duplicate of https://github.com/rubyforgood/Flaredown/issues/480 no?

lmerriam commented 2 years ago

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.

benlangfeld commented 2 years ago

Thanks @lmerriam . I'll close this as a duplicate and look into it in #480

lmerriam commented 2 years ago

@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.

lmerriam commented 2 years ago

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.