At 14 crashes per 1000 you probably won't see many crashes on average but in reality it's likely there are a number of people that have something in their settings or resume file that cause it to crash much more frequently, such as a terabyte+ sized torrent with tens of thousands of files where they select every other file to download (a possible crash I'm looking in to now). We like to shoot for 4 to 6 crashes per 1000. Any time your machine goes in to high CPU load because of our client please feel free to send me a sample along with a screen shot and an explanation of the conditions under which this is occurring including OS version, machine setup and wether or not any of the target locations are on an external or network drive. Any information we get can help us nail down the problem. The client is pretty good about choosing peers from the list available from the trackers, DHT and peer exchange. Tweaking the limits on a per torrent basis up or down when there are user storms may not be as helpful as you might think as everybody is competing for a small number of peers with a set maximum bandwidth but if it's a feature you think would be popular you may want to post it on uservoice: http://utorrentideas.uservoice.com/forums/58959-torrent-mac http://utorrentideas.uservoice.com/forums/47263-torrent-for-windows Since this feature would require some core changes to implement I would recommend posting it on the windows client board since they see much more traffic. If it makes it in to the windows client and in to our core code it will be a trivial addition to the mac client.