![]() ![]() Regardless of using Google Drive File Stream (GDFS) to help work around the slow performance of duplicacy check, I think duplicacy should still support the -threads option. Having kernel drivers in an O/S is a huge risk in this regard, ultimately to work around a duplicacy issue in that threading isn't universally supported in all commands. ![]() At times they don't update very quickly, leaving users "stranded" for some period of time (often many months or longer). In the case of Google, this is "risky" at best. When a new O/S comes out, sometimes software doesn't run properly under it, and you need to wait for software vendors to update software to work with newer releases. However, another concern has come up: designing a backup system dependent on something like Google Drive File Stream can make it very difficult to deal with new versions of Mac OS/X (or Windows for major updates, etc). I didn't have time last night to look at this, and I still plan on doing so. ![]() But some smallish number (like 8-16 threads), should be under the limits. Yes, GCD has a limit to the number of concurrent operations. The duplicacy check command should support the -threads parameter to allow multiple threads to collect the chunk data with considerably less delay. Network/backend delays ultimate cause a dramatic speed difference. Meanwhile, GCD chunks are generally broken into 256 directories, and each of those directories need directory operations performed on them. Azure implements an API that allows Duplicacy to get all the chunk metadata in a very small number of API calls. Investigation showed that the difference was in the storage backends. Meanwhile, GCD took a whopping 31 1/2 minutes. Note that Azure took 1 minute 24 seconds for the operation. All chunks referenced by snapshot taltos at revision 1 existĪll chunks referenced by snapshot taltos at revision 2 existĪll chunks referenced by snapshot taltos at revision 3 existĪll chunks referenced by snapshot taltos at revision 4 exist ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |