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
This code is in time out #21319
Comments
Try
|
Hello, i use the last version V 0.4.5 24af002.20fd795, I need to update again? Thanks |
Yes, you need to update again. |
Latest V is Since V is still changing often, it is always best if you see an error to immediately do |
I launch "v up" 3x or 4x times by day, so it's strange ;) |
That screenshot is too dark for me to read, so I'm not sure what you're saying is the problem, there. |
Please try with 250001 not
Please try with 250001, on your capture you miss one 0 |
How much RAM do you have? I did start it with the higher number, and let it run for a couple of hours... still no output. So I checked free memory, and saw it going down bit-by-bit over time. That's what happens with recursive routines like you have. However, Ctrl-C stopped it immediately, no problem. So I tried running with different numbers. With 30000, I saw
With 50000, it got much worse... as it in has been running over an hour, and hasn't finished, yet.
Quite a jump from 3.5 minutes to 1 hour 19 1/2 minutes for only 20000 more... |
I have 16G ram , but go version is executed instantly, see time You can check here ; https://programming-language-benchmarks.vercel.app/problem/edigits |
V doctor:
What did you do?
v run edigit.v 250001
Tested from this bench source : https://github.com/hanabi1224/Programming-Language-Benchmarks/blob/main/bench/algorithm/edigits/1.v
What did you expect to see?
n (fish: Job 1, './edigit 250001' terminated by signal SIGKILL (Force to quit))
What did you see instead?
The text was updated successfully, but these errors were encountered: