CPU / Memory Leak Workers + Maybe Async Local Storage?
This clearly looks like a (memory) leak somewhere right? Or what could this indicate? We've weird, sudden CPU / memory spikes that always kind of build up like this and no idea how to debug this. Switched to unbound from bundled just to keep our API awake, would be great if the tail workers could tell us how much CPU a request consumed
1 Reply
Could this be async local storage getting full in the same isolate?
We do have a lot of requests coming in, every 5 seconds * amount of drivers online, and use async local storage to attach contexts to logs