-
Notifications
You must be signed in to change notification settings - Fork 298
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
evalv3: OOM and signal killed (64GB) #3334
Comments
I wrote this quick script to see if I could find anything obvious, but it doesn't appear that any individual directory causes this. It seems maybe to be a culmination of all of them? There are some pretty large spikes in memory usage. ❯ for dir in */; echo "$dir:" && CUE_EXPERIMENT=evalv3 go run cuelang.org/go/cmd/[email protected] export "./$dir" Some of those spikes are like 10 gigabytes.... |
If it helps - the latest stable release without using evalv3 takes at most 2GB for everything all at once ( ❯ cue version
cue version 0.9.2
go version go1.22.5
-buildmode pie
-compiler gc
-trimpath true
DefaultGODEBUG httplaxcontentlength=1,httpmuxgo121=1,tls10server=1,tlsrsakex=1,tlsunsafeekm=1
CGO_ENABLED 1
GOARCH amd64
GOOS linux
GOAMD64 v1
cue.lang.version v0.9.2 |
I don't know if this pprof info is helpful.
|
Some updated numbers, as of CUE 655236e:
We see a similar issue with a few other medium to large projects when using the new evaluator. The current work in #2854 and particularly #2853 should help significantly here. I will update this thread once more progress has been made, as we are actively merging improvements into master. |
I have finally been able to reduce a bit of CUE which seems to OOM my machine where evalv2 definitely did not: #3509 |
Still seems to happen as of 0005c22. |
I again reduced part of this project into another performance issue to be fixed: #3633 |
What version of CUE are you using (
cue version
)?Does this issue reproduce with the latest stable release?
Yes.
What did you do?
After following this to fix another issue, I thought it would be interesting to try the new evaluator again.
#3330 (comment)
uhthomas/automata@5a1a4fe
What did you expect to see?
Successful build.
What did you see instead?
OOM, signal killed.
The text was updated successfully, but these errors were encountered: