We reacently added a Serilog sink to push events into Honeycomb that's built on top of Serilog's Periodic Batching sink, but when deployed we see the memory usage skyrockets.
After managing to get a memory dump we see the main culprit being the _queue within the PeriodicBatching sink to be the one hogging it.
This behaviour is seen consistently across all instances and we wonder if it might be a bug in the sink or queue implementation.
