Comment by ants_everywhere
Comment by ants_everywhere 4 days ago
> even though the majority of the time was spent on HTTP calls?
I'm not sure why this detail is relevant. The CPU it consumes is still CPU. Hypothetically, if a rewrite saves $100 million annually in compute, why does it matter that the majority of its time isn't spent in compute? It's still $100 million.
I took that to mean the tool was IO-bound, so it wasn't using much CPU to start. So if there was even that tiny sliver of slack CPU (and that's almost definitely the case on a desktop or other dev machine), then saving that tiny bit of CPU actually saved no money, since it was already riding on the spare capacity of other investments. That just leaves the cost in engineer-hours to rewrite the program.