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

fix: Aggressively GC wasm instances #428

Merged
merged 1 commit into from
May 3, 2023
Merged

fix: Aggressively GC wasm instances #428

merged 1 commit into from
May 3, 2023

Conversation

ospencer
Copy link
Contributor

@ospencer ospencer commented May 3, 2023

No description provided.

@ospencer ospencer requested review from callahad and javorszky May 3, 2023 16:59
@ospencer ospencer self-assigned this May 3, 2023
@callahad
Copy link

callahad commented May 3, 2023

Looks not-unreasonable, but let's hold off on merging until we fix issue with occasional stuck workers since it's easier to trigger that failure mode without this patch in ;)

@javorszky
Copy link
Contributor

Looks okay, and I agree with @callahad on holding on to this. Alternatively we can give the VM significantly more memory to use

@ospencer ospencer merged commit 49c96d2 into main May 3, 2023
@ospencer ospencer deleted the oscar/gc-tuning branch May 3, 2023 21:10
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

Successfully merging this pull request may close these issues.

3 participants