-
Notifications
You must be signed in to change notification settings - Fork 541
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
Log when NN eval takes longer than one second. #1768
Labels
good first issue
Good for newcomers
Comments
Now I suspect that's actually the tablebase probing that takes so long. So it would make sense to add similar logging there too. |
Does NN evaluation happen here? |
It's called here: Line 2192 in 08b41c4
There are many backends, all of them implement |
KarlKfoury
added a commit
to KarlKfoury/lc0
that referenced
this issue
Aug 30, 2024
…me > 1s fixing issue LeelaChessZero#1768
what about tablebase probing? i assume it happens here ? |
KarlKfoury
added a commit
to KarlKfoury/lc0
that referenced
this issue
Aug 30, 2024
fixing LeelaChessZero#1768 we brought one
KarlKfoury
added a commit
to KarlKfoury/lc0
that referenced
this issue
Aug 30, 2024
adressing issue LeelaChessZero#1768
KarlKfoury
added a commit
to KarlKfoury/lc0
that referenced
this issue
Aug 31, 2024
KarlKfoury
added a commit
to KarlKfoury/lc0
that referenced
this issue
Aug 31, 2024
…ime > 1s adressing issue LeelaChessZero#1768
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
During WCCC and testing, we saw cases where the search couldn't stop for up to 27 seconds.
We suspect that it's backend that takes so long to compute a batch.
It would be nice to output a message to a log file when that happens, when NN takes longer than a second or so.
The text was updated successfully, but these errors were encountered: