Regarding them being overwhelmed… transferring at 1MByte/s here (which is the 10MBit/s throttling that they state) across multiple transfers. ]]Ĭould be that connections to California are throttled… or something… but certainly from here, behaviour is just find at present, for me - despite these messages appearing, files still transfer and all is happy bunnies. In any case, the ‘Request Time-out’ message is a benign part of the protocol and should not (if I’ve understood what’s going on correctly - see for my understanding) affect the transfers. On the other hand, with a lot of small files, there is an advantage to having a larger number of transferrers (and checkers) so that there is always something doing work. If you have very large files and many transferrer threads configured, the transfers will be worse because all the big files will be contending for the 10mbit/s rate limiting and it would be better to have fewer transferrers in such case, so that a few large files transfer. I had some issues with the authentication tokens failing due to running the process on multiple machines, and the prior authentication not renewing properly (I guess), but just re-authorising solved that. I’m currently transferring a lot of files and all is working fine here (UK) for me - maybe I’m sucking all that bandwidth and leaving you with none (no that’s really not likely to be the case).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |