rafi Posted February 19, 2006 Report Share Posted February 19, 2006 Something strange related to the latest bug of B 426->7 of multiple hash errors: this was related to the diskio.coalesce_write --> I've noticed that when running B 425 and B 427 - this setting is being reversed. How come ? does it reflect a problem ? I also suggest to save for each torrent - the "wasted" data + "# of hash fails" that are currently shown only during DL. Those should be kept as we do keep a record of the data size and average speed. Link to comment Share on other sites More sharing options...
Firon Posted February 19, 2006 Report Share Posted February 19, 2006 b426 turns coalesce writes on by default, and it's still on in b427 because it helps reduce writes (one part of the disk i/o improvements, but not the only one) Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.