I definitely don’t suggest the init command pre-populate these settings based on recommended values. Would Duplicacy benefit from having a different thread count for source and destination? If not, why does copy already have both -download-limit-rate and -upload-limit-rate options?īTW I’m not overly attached to this idea… I just threw it out there as a suitable enough improvement - a compromise to having hard-coded defaults for storage backends. The lesser of the two applicable values? What if one isn’t set? Could it make a more intelligent choice? Might seem straightforward, yet not necessarily so. We have source and destination threads, upstream and downstream values for each. Since the set command exists already for similar purposes, feature creep is minimal, and my proposal was strictly for thread counts and bandwidth limits.īut one problem with the idea I can think of already is deciding which thread amount and bw limit to use for the copy command. And if you continually switch connections, you might simply choose not to ‘set’ anything at all. is an American cloud storage and data backup company based in San Mateo, California. With you on the Unix way, I don’t think it precludes the possibility to allow defaults to be overridden with a command line switch, especially in exceptional situations as above. (April 2021) ( Learn how and when to remove this template message) Backblaze, Inc. You might want to alter number of threads depending on your connection (LAN vs LTE) instead it shows: Backblaze support is available as an add-on follow this link to get it, then it wants me to purchase it. When selecting Backblaze, there are no boxes shown to enter Bucketname, etc. This adds unnecessary complexity and ambiguity and bloat and increased possibilitity to misconfigure things. Jat 6:02 pm 1184306 bob41 Participant I have activated the premium plugin on a new site. Backblaze offers a mobile app but doesnt let you backup your phone. Command line utility is a backend, and it’s interface shall be clean, logical, and unambiguous, without 20 different ways to accomplish the same things. Backblaze is an unlimited backup service thats easy to use but has a few hiccups. However I still disagree that we should be adding redundant features just because it seems to simplify one particular use case: this is what front ends are for. The current implementation of it as a command line argument is therefore the most appropriate. You might want to alter number of threads depending on your connection (LAN vs LTE), and therefore it should not be part of storage configuration, it shall be function of the environment. Get access to 100M+ contacts on Adapt.io. Whether it is right thing to do I’m still not sure. Find the Backblaze companys support team/department contact details such as business emails, phone numbers, web address and other details. When you put it this way, yes, that proposal does make some sense if we think of it not as a “another way to specify command line arguments to save time typing” but instead “treating number of threads as part of storage backend configuration”.
0 kommentar(er)
