Vladimir Dementyev
Vladimir Dementyev
As I understand, the memory grows over a long period of time, right? Could you please show the latest spike chart (around 9/30) in a higher resolution? (And, ideally, RAM,...
Thanks for sharing! Given that other we don't see anything suspicious in the other metrics around the spike, I'd suggest a memory bloat situation (still unclear what cases it): memory...
Thanks for the data! May I ask to share the `clients_num` / `goroutines_num` / `client_msg_total` data for the same 2 days period? I wonder what causes local memory usage spikes...
Please, try just published v1.6.7 that has some possibly related fix (mutexes-related).
@d4rky-pl (while you're around 🙂) Any updates on this?
Thanks! Could be related to #263 (same fix). Let's check again after the next release is out.
> the logidze_logger_after function appears to be generated even without passing an "after-trigger" flag. Is this intended for --update? Yes. We generate all the functions on install/update, so you can...
Logidze can handle JSON(B) types but it doesn't create diffs for them (so, they're kinda treated as strings).
Just to confirm: the first charts show Redis memory usage? > not sure if it's relevant but we're using [graphql subscriptions](https://github.com/anycable/graphql-anycable) only Yeah, possibly related. AnyCable GraphQL stores subscriptions information...
@d4rky-pl Thanks for sharing the AnyCable server configuration! As I can see, Redis is only used for pub/sub, so no memory should be retained. I wonder if we can get...