This is what i've experienced so far (I also serve about 200 people): When you limit the number of simultaneous downloads, the first person to send a request uppon a file completion gets the spot, but if someone loses the connection to the server and meanwhile someone sends a request, that will also make them steal the spot (remeber download managers send requests every so often when trying to connect to the server). Speed wise, technically seeding 100 people at the same time is faster in the sense that you get more MBs sent overtime (from the servers point of view), but this will slow down the downloading process individually for users (obvious). It's a matter of if seeding too many people at the same time takes the users too much of their time to download, then cutback at the number of simultaneous downloads allowed. LAN wise speeds can go pretty high up so no need to limit, although I find that when 15+ people are downloading at the same time the use of possible bandwidth will probably hit 100%, in my case 8MB/s (LAN).