@boggle this is what it does, every 30 seconds, it scans 100 nodes. The reason for the low number here (which is mostly pulled out of dark places) is that I thought it'd be better to play it safe here. If you hit a supernode here, and we go into each rel to check property distribution and so on, this could have a very negative impact on cache usage. Same for very very large properties. So I thought it'd be better to leave it low to start out. We may want to adjust this though if we find it takes unacceptably long for the heuristics to stabilize.