Hey y’all, I’ve been plotting away the last few weeks and I just stumbled across the wiki topic that talks about how the speed of your lookups have to be < 5 seconds and preferably below 2 seconds. How do I find this information?
I’ve checked debug.log and there’s nothing about speed of my look ups. I could not find a line like this -
07:02:41.663 harvester src.harvester.harvester : INFO 1 plots were eligible for farming f53c496e80... Found 0 proofs. Time: 0.00500 s. Total 8 plots
… as mentioned in the wiki.
I am using swar’s plotting manager if that is relevant.
I actually found the entries in my log files now after a deep dive -
WARNING Looking up qualities on G:\plot-k32-2021-05-21-10- .... took: 19.05907130241394. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on F:\plot-k32-2021-05-20-15- ... took: 19.129594326019287. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on G:\plot-k32-2021-05-20-15- ... took: 19.093616724014282. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on F:\plot-k32-2021-05-20-15- ... took: 19.140445709228516. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on G:\plot-k32-2021-05-20-15- ... took: 19.15084981918335. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on F:\plot-k32-2021-05-20-15- ... took: 5.4761223793029785. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on H:\Plots\plot-k32-2021-05- ... took: 11.460636138916016. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on H:\Plots\plot-k32-2021-05- ... took: 11.340665340423584. This should be below 5 seconds to minimize risk of losing rewards.
WARNING Looking up qualities on H:\Plots\plot-k32-2021-05- ... took: 11.41548466682434. This should be below 5 seconds to minimize risk of losing rewards.
How do I find out what is causing this? And how would I go about fixing it?
Your logging level (set in the config.yaml file) needs to be set to INFO to see the entries you are looking for. A restart of the Chia software is needed for the change to take effect.
Hey @WolfGT, I changed the level to INFO and below are my findings.
INFO 0 plots were eligible for farming b76226ef6a… Found 0 proofs. Time: 0.00798 s. Total 103 plots
Why does it say that 0 plots are eligible for farming? 
Normal. For more information, here is the paragraph in the Chia FAQ
What is the plot filter and why didn’t my plot pass it?
Farmers compute a plot filter based on the signage point, their plot id, and the sub-slot challenge - which are hashed together to create the plot filter bits. If the plot filter bits start with 9 zeroes, that plot passes the filter for that signage point, and can proceed. This disqualifies around 511/512 of all proofs of space on the network, for each signage point. There are 4608 * 2 or 9216 signage points per day so the average plot should pass the filter 18 times per 24 hours on average. Once a plot passes the plot filter it then competes for the best proof of space with every other plot that also passed that plot filter for that signage point. For reasons that aren’t super simple to intuit, the only thing each plot is competing on is to have the best proof of space and thus the chances of getting a reward depend on total size of plots on the farm - even with the plot filter in place.
As long as the plot passes the filter, and do not have any internal file errors, the plot will always be eligible to compete for the best proof of space. Moving the plot to another directory or server will not change its eligibility.
Please note that the speed of your lookups when passing the plot filter should be below 5 and preferably below 2 seconds. When you actually win a reward, your drive will have to do more lookups than these, so it’s important that the the lookups are happening fast.
1 Like
Got it, thank you for clearing that up! @WolfGT
If I find that all my lookups are taking between 5 and 10 seconds, what can I do to resolve this?
You should have lookup times like the above when no proof is found or something like the below line (taken directly from my farmer log)
1 plots were eligible for farming 616c18fc9c… Found 1 proofs. Time: 1.23190 s. Total 261 plots
when a proof is “challenged”. If you are on a pool, they get the “challenge request” as I am calling it. The challenge at the pool is where you get the stale or rejected partials. I don’t know what either mean other than something went wrong in what I am calling the challenge.
x plots finding y proofs in 5 seconds is fine. 10+ seconds is not good. x = number of plots eligible and can be more than 1, I’ve seen up to 4. Y = number of proofs, and it can be as high as the number of eligible plots.
Check your drives and make sure they aren’t too slow. That shouldn’t matter though. Then check your internet and internal network for latency. The speed of the network is one thing. The latency and jitter is a problem sometimes. Check latency/internet speed on fast.com. High latency can be an issue.
Thank you!
I went to fast.com and got 15ms unloaded and 235ms loaded latency. Is this okay?
Those numbers should be fine. My latency unloaded is 30 and loaded is 650. I am not getting above 1.5xxx second proof submission times. Maybe a hardware issue?
Weird.
When I look at my pool, it has always showed that 100% of my partials are valid. Do I need to worry as long as that stays 100%?
1 Like
You’re right. You don’t have to worry about it as long as 100% of your partials are valid. The invalid partials are the ones that took too long to respond.
You can also monitor your lookups time with Chiadog if you want to. It will automatically grab all your logs and show your average lookups time. I am on Raspberry Pi 4 with 20 drives(SMR) through USB hubs, my average lookups time is 0.62 secs.