I have some ideas how to improve this also.ĭisclaimer: I work at Backblaze so I'm biased. So you get "bursts" of speed, but it kind of slows down to "steady state" after that. :-)ĪLSO, totally unrelated to the above situation, I've seen my computer slow down after a little while because it is CPU limited, and when the fans kick on and the CPU heats up, these modern processors slow down their clock rates to prevent overheating. I'm going to continue improving this in the future. What this all means is there is a "performance notch" where the performance may not be as good for files between 100 MBytes and let's say 500 MBytes. Now remember it is transmitting in file size order, so when it reaches files that are 120 MBytes in size Backblaze can then use 12 threads, when it reaches files of size 500 MBytes in size it can use 50 threads, and so on. Now here is where this can slow down a little: if you have a 110 MByte file, Backblaze can only get use out of 11 threads, because that's all the chunks it has to send. The threads are each assigned a 10 MByte section of the file called a "chunk". And Backblaze's threading changes for files less than 100 MBytes and files larger than 100 MBytes.įor files less than 100 MBytes, a thread is assigned a file, so you can transmit up to 100 files, each of which is say 99 MBytes in size all in parallel.įor files larger than 100 MBytes, Backblaze focuses on one file at a time. First of all, Backblaze backs up in file size order, small files first. There are several reasons this can occur. I went back to 30 MB/sec and even less this morning. Disclaimer: I work at Backblaze and did some of the performance improvements in 8.0
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |