Hello! > Instead, we do it every base_reachable_time/2 **ticks**, > i.e. every 15 ticks, which is (at 300 ticks/second) roughly 20 times per > second (plus-minus some timer period scheduling leeway, which lets it get to > 17.7/second as in my case), which sounds way too high.
No, the timer ticks each base_reachable_time/2/size_of_hash_table jiffies. At time when this code was written, size of hash table was fixed and it was 32, which means timer ticked each ~0.5sec, which was reasonable. Now it is dynamic, hash table size starts from 1 and grows. Obviosuly, it can overgrow all the reasonable limits. > At HZ=1000, this timer would be invoked around 60 times per second, then?? And even more if hash table is large enough. Obviously, it should scan more than one hash bucket per tick to keep timer frequency reasonable. The question is what is reasonable? Alexey _______________________________________________ Power mailing list [email protected] http://www.bughost.org/mailman/listinfo/power
