Open Jacek-ghub opened 3 years ago
Jacek-ghub
commented
3 years ago By the way, I would suggest that you put a screenshot and a short How-To for that heat map tool in the readme, so people that visit your page can see that. I put some links to your page on the main Chia Issues tab.
Jacek-ghub
commented
3 years ago Would there be a possibility to also show how long it took for those blocks with proofs found. Currently, they are all dark blue, with barely visible black numbers.
A quick question about those found proofs. Are those only happening for plots that belong to some third party pools? I had them in self pool for a week (since introduction), and had zero found proofs. Within minutes of joining a third party pool, I see those showing up.
With the release of Chia 1.2.0+, there is a substantial degradation of lookup times on all platforms. This is where harvester heat maps actually shine, by quickly highlighting those problems (I run them 24/7). If not that tool, trying to isolate those problems is really hard.
In my case, I share chia's log folders over the network, and have just one box show my harvesters. This actually addresses the issue people had, where they are using different OSes as harvesters (no need to run it on the harvester sitting on a non-Win OS).
One person also brought up a question, how the heat map lookups are done. He splits his logs by modules, so there is not all plotting info there. I assume that heat map module is only looking for those timeout lines, if not maybe it could be modified to do so. It would be nice to write down which lines are needed, as sometimes it may be beneficial to extract those lines to yet another log file, in case the main ones are growing really fast (e.g., with DEBUG option).
Another thing would be to share the PSCP heat map code and provide it as a separate module (for those that want lite-install). I know, it doesn't really matter whether it is also provided as a separate module, but maybe more people will be happy with that solution. This is a low priority, if at all task.
I was checking those threads around those timeouts, and to me that heat map tool may have a lot of value. We all know that Chia code is not the best, and tools like that can keep it in check (giving early warnings - gave it to me, and I posted about it there - unfortunately, no Chia support provided any feedback).
I guess, people would also appreciate similar tools to that, that would pull the concise info from all modules. The Chia UI is rather crappy, so that doesn't help, when the plumbing is also not that good.