Bug 515052

Summary: monsoon 0.2.0: endgame is slow
Product: [Mono] Mono: Tools Reporter: Charles Kerr <charles>
Component: MonoTorrentAssignee: Alan McGovern <alan.mcgovern>
Status: NEW --- QA Contact: Alan McGovern <alan.mcgovern>
Severity: Minor    
Priority: P5 - None    
Version: unspecified   
Target Milestone: ---   
Hardware: x86-64   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Charles Kerr 2009-06-22 00:30:44 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4) Gecko/20090427 Fedora/3.5-0.20.beta4.fc11 Firefox/3.5b4

This is another issue I found with Monsoon while doing the BitTorrent client tests I mentioned in ticket #515018. I was downloaded a Linux CD twice with Monsoon, and both times the download speeds were pretty good until the very end, and then speeds tanked.  In both runs, 99%->100% took longer than 90%->95%.

I haven't read the code, so this is only a guess, but my guess is that MonoTorrent is too conservative about sending redundant requests during endgame, so nonresponsive peers slow down getting those final pieces complete.

(o/t: Alan, just so you don't think I'm picking on Monsoon with these tickets, I'll give you some good news too... Monsoon 0.2.0 used *half* the memory that Deluge 1.2.0-dev used... :)

Reproducible: Always

Steps to Reproduce:
1.
2.
3.