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

Implement feedback for when a GC happen #5

Open
danielfireman opened this issue Oct 23, 2018 · 0 comments
Open

Implement feedback for when a GC happen #5

danielfireman opened this issue Oct 23, 2018 · 0 comments

Comments

@danielfireman
Copy link
Contributor

danielfireman commented Oct 23, 2018

There are quite a few runtimes which developers can not disable the GC. Even though the proxy is conservative when setting the heap consumption limits, that can still leave room for mistakes. In those cases, the upper limit must decrease.

That needs to come from a mechanism which tells the proxy that one or more spurious GC had happened. Instead of checking every answer, we could add another field from the memory check message. That could return the number of spurious GCs that happened since the last check.

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

1 participant