The "Update active torrents only" option is a nice way of reducing the
chattiness of the RPC protocol. In my scenario using 3 second update over one
minute duration, data is reduced from ~37MB (!!) to ~3.3MB over
An improvement would be to do a global update (to get scrape info etc) on the
same cycle as the "Minimised update interval"
This seems like a reasonable heuristic.
Original issue reported on code.google.com by reardo...@gmail.com on 11 Sep 2011 at 11:11
Original issue reported on code.google.com by
reardo...@gmail.com
on 11 Sep 2011 at 11:11