4 writes out of what, 3000? For something you'll need to do once or twice ever? It's fine. You might not even eat your whole Drive Write Per Day quota for the upload duration, let alone the entire month.

> the technical limits of the technology that I had at home (PON for the time being)

Isn't that usually symmetrical? Is yours not?

▲

bayindirh 7 hours ago | parent | next [-]

> 4 writes out of what, 3000?

Depends on your device capacity and how much is in actual use. Wear leveling things also wear things while it moves things around.

> For something you'll need to do once or twice ever?

I don't know you, but my cloud storage is living, and even if it's not living, if the software can't smartly ignore files, it'll pull everything in, compare and pass without uploading, causing churns in every backup cycle.

> Isn't that usually symmetrical? Is yours not?

GPON (Gigabit PON) is asymmetric. Theoretical limits is 2.4Gbps down, 1.2Gbps up. I have 1000Mbit/75Mbit at home.

	▲	Dylan16807 6 hours ago \| parent [-]
		> I don't know you, but my cloud storage is living But you're probably changing less than 1% each day. And new changes are likely already in the cache, no need to download them. > if the software can't smartly ignore files, it'll Backblaze checks the modification date. > GPON (Gigabit PON) is asymmetric. Theoretical limits is 2.4Gbps down, 1.2Gbps up. I have 1000Mbit/75Mbit at home. 2:1 is fine. If you're getting worse than 10:1 then that does sound like your ISP failed you?

▲

jonhohle 6 hours ago | parent | prev [-]

How do you know how often those files need to be backed up without reading them? Timestamps and sizes are not reliable, only content hashes. How do you get a content hash? You read the file.

	▲	NetMageSCW 6 hours ago \| parent \| next [-]
		If timestamps aren’t reliable, you fall way outside the user that can trust a third party backup provider. Name a time when modification timestamp fails but a cloud provider will catch the need to download the file.
	▲	Dylan16807 6 hours ago \| parent \| prev [-]
		Backblaze already trusts the modification date.