Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

high memory usage #59

Open
bloep opened this issue Oct 1, 2020 · 1 comment
Open

high memory usage #59

bloep opened this issue Oct 1, 2020 · 1 comment

Comments

@bloep
Copy link
Contributor

bloep commented Oct 1, 2020

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.

image

Maybe we have a memory leak issue here?

@itsgoingd
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants