Scanner has been simulating for hours now (No memory leaks, and no crashes evident)
Last update on .
But at the current settings it could be as much as 20 minutes (in a worse-case scenario) before the scanner notices an offline low-level branch. It's currently taking ~4% of CPU, so I can likely rachet up the maximum group-ping frequency to 5 minutes or so and still have acceptable performance. Will need to work on balancing that.
Think I'll hit the hay now and get another early start tomorrow.
Pingbacks are closed.
Comments are closed.