One example I'd find reasonable, perhaps the Apple Silicon M family has a shot at it, when comparing the energy draw diff (less than half of Intel's equivalent) multiply by the adoption at scale.. maybe that.
One more straightforward that definitely have a chance at achieving the effect: LED lightbulbs: huge consumption reduction, huge scale.
[1] for example https://about.gitlab.com/blog/2019/02/13/delayed-replication...
Let’s say a full backup takes 3 hours and an incremental one 3 minutes.
Let’s say I want at most 3 hours of lag in my backups. That would mean 3 hours every 3 hours. That is about 720 hours per month for a full backup or 720 minutes (12 hours) for incremental backups. Let’s say we Still do a full one once a day then that is still 102 hours per month in total.
Even if you do 1 incremental per hour you’d end up at 36 hours a month. If 3 minutes were true for the every 3 hour scenario, the every 1 hour scenario would also mean shorter backups so maybe 1 minute, which adds up to 12 hours.
All this to say that it might be more efficient.
I'm being dramatic obviously but like... less CPU cycles, less network bandwidth, etc. etc.
If adopted by top 100 "large" database/operations, is it as much as like 100 people giving up their gas/petrol/diesel car?