The queing feature actually improved the performance on your side of things. When your slots are busy the requests are queued.


"So what's the use of queueing?

- It prevents a "bombardment" of download and retry attempts. Each attempt, it needs to send out the "503" error message. Although it seems little, a popular file can cause a lot of these requests and eat a bit of the available bandwidth, and available incomming ports (should there be a limit, depending on, say, firewall, proxy, bandwidth throtling systems). If it is queued, the client doesn't need to retry but simply wait...

- It gives the end-user a visual representation when to expect the file. With current "retries", the end user just knows he or she will NOT receive the file at all, until at least a successful retry. Most likely, he'll start clicking more of the similar results and try those, maybe ending up with 20 possible servers, creating the previous scenario. When it is queued, the end user will know that his request was successful, the file is indeed available on the server, and there's a greater chance the server will send it to him once the server is ready to do so.

- It allows a single file to be queued at multiple servers."

http://www.leeware.com