vdbergh
vdbergh
I suspect that something green + ltc would need an index since it is the intersection of two large sets, hence not easy to compute by scanning.
To me 300ms seems fine for a complex query (if I understand correctly your numbers).
Here is an issue about the current indexes #1243 . It also contains information on how to debug indexes (which is tricky in mongodb). EDIT: also see #1242 .
I think one should use `explain` to see if the new indexes are used. Unfortunately I have no time now. But see #1242.
Hi @ocaio thanks for your posts and for posting the cutechess-cli binary! It is a bit sad that the rPI seems to be too slow for Fishtest though (although it...
That's a good point which I had not thought of. So the crashes/time losses should be at least for different runs and probably even for different users (in case a...
So I would go for three consecutive crash_or_time events from three different runs from at least two different users.
There are already the info and error fields in the reply. Please use the info field. It will be handled correctly.
There is also the issue that the messages depend on the run that is being handled, which is suppressed in the feedback. In general I think most messages are uninteresting...
I think there are only two serious misconfigurations a worker can do that may cause it to get no runs. Setting minthreads > 1 or setting maxmemory too low. To...