So AI means 14x the checkins? That's not 14x features completed, but still... wow.
So AI means 14x the checkins? That's not 14x features completed, but still... wow.
While that is (hopefully) the upper end of the distribution, several companies have loudly encouraged engineers to light tokens on fire to the AI gods, so it only takes a handful of the devout to push up the average in gas town like ventures.
Spread over a year, roughly estimating a generous 4 kbytes of data per commit, comes out to a throughput of a little under 2 MB/s.
Of course, it isn’t spread out uniformly and there is also a lot of hashing and other things going on.
Maybe pulls and clones drive more I/O ?
That's also just assuming the good-faith usage. There are probably plenty of adversarial and poorly behaved scrapers that are putting additional load on the system.
Even if they had 10 billion users with 10 billion repositories it shouldn’t be a big deal on a home PC.
For instance with OpenClaw and similar, they often simulate institutional and short term memory with markdown files in folders. Other tooling that runs companies using agents as staff, for example, do the same - but also with files for inputs, outcomes, handovers etc.
All of this means a lot of extra churn as these kinds of files can be changing with every interaction not just every traditional commit point.
We had it internally with our teams that open a PR to then push like 10-20 more commits but never actually interested in the client builds etc. turned out they opened the PR as a checkmark/ way to share the current state. We set cooldowns and auto cancel for the ci. And then there is the developer who uses the CI compute to run tests instead of running them locally for various reasons. We had to remind that compute isn’t for free.