You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sometimes the browser (e.g. Safari) shows a banner whether the site has a high memory usage.
In my testcase with a fresh open instance of the clockwork app with around 10 tracked requests the dev tools tells me a vm instance size of over 140MB.
For comparison github has around 10-20MB.
Maybe we have a memory leak issue here?
The text was updated successfully, but these errors were encountered:
Hey, indeed the memory usage is far from perfect. It also depends a lot on how large your metadata is.
The most obvious issue is, we never unload old requests. So long running Clockwork instance will eventually run out of memory. This should be pretty easy to fix, will take a look before 5.0.
Another idea would be to unload all inactive large requests and re-initialize them from json when selected in the UI. Would need to experiment with that to see if it's worth it.
As far as memory leaks or more low-level optimizations go, I will need to do some more research. Vue is a limiting factor here, as we can do very little with it's internals. Vue 3 should be a major improvement in performance and memory usage. But it's really tricky to update the Clockwork codebase, so that will happen in 5.1 at earliest.
Hi,
sometimes the browser (e.g. Safari) shows a banner whether the site has a high memory usage.
In my testcase with a fresh open instance of the clockwork app with around 10 tracked requests the dev tools tells me a vm instance size of over 140MB.
For comparison github has around 10-20MB.
Maybe we have a memory leak issue here?
The text was updated successfully, but these errors were encountered: