![]() Let’s put things into perspective: you need a speed of 25 megabits per second to have a seamless Ultra HD quality and receive a crystal crisp image. Here are the internet connection speeds that Netflix recommends for its services:ģ.0 Megabits per second – Recommended for SD qualityĥ.0 Megabits per second – Recommended for HD qualityĢ5 Megabits per second – Recommended for Ultra HD quality We checked the requirements of Netflix, one of the world’s most popular movie and TV series streaming provider. The best way to illustrate this is perhaps with a video streaming example. We achieved that through a network of collocated proxy servers and an entirely new data transfer protocol – we call it PUDP – which we developed in-house.īut we’ve also tweaked the speed, at which you can download files from pCloud – our Free plan users can download files with up to 40 megabytes per second, while Premium, Premium Plus and pCloud Business plans subscribers can take advantage of a download speed of up to 80 MB/s (of course, this depends on the speed of your internet connection). ![]() When I look at the transfer in the config window of Mirall, it appears that the upload itself is very fast ( open called for ownclouds:///owncloudbeta/remote.php/webdav/Liban/Liban (38).JPGġ1-28 15:22:33:331 oc_module: Stating directory ownclouds:///owncloudbeta/remote.php/webdav/Libanġ1-28 15:22:33:331 oc_module: Dir ownclouds:///owncloudbeta/remote.php/webdav/Liban is there, we know it already.ġ1-28 15:22:33:331 oc_module: PUT request on /owncloudbeta/remote.php/webdav/Liban/Liban%20%2838%29.JPG!ġ1-28 15:22:33:331 oc_module: Sendfile handling request type PUT. ![]() It takes 3.5 seconds to upload a picture of 1,39 Mo. Just for information, I just tested Mirall 1.5 1.4.2 against OC 6 RC (realeased today). (This is probably tricky because as far as I understand, the way csync handles transfers is limited to handling only a single file at a time.) do a single PROPFIND for a collection and evaluate all its members for changes from that one multistatus response (later, the PROPFIND depth could be increased even further, in theory up to requesting the complete remote hierarchy en bloc).Īlso, wouldn't it be possible to extend the owncloud implementation of the PUT command to support passing the modification time as a request header when uploading the file so that no additional PROPPATCH request is necessary after the upload?Īs suggested above, when actually transferring file data, batching several transfers in parallel could increase throughput. ![]() Maybe as a first step it would help to batch the metadata operations concerning the same collection, i.e. This also already affects walking the the remote filesystem when checking for modifications. I think the problem is primarily due to the overhead per file/collection (reading/setting props, caching the file locally etc.) which ends up being more costly than the actual data transfer for small files and collections. IMHO this also has to do with having a deep directory hierarchy. I can confirm this issue (OC 4.5.5, Linux client 1.1.4).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |