|
|
|
|
|
by vidarh
872 days ago
|
|
Not just the workstations. You really need to factor in the other carbon output of those developers for the time spent on the project too, not just the tools. And you then need to consider to what extent any performance saving will be efficiently captured as reduced power use. But, yes, fully agree. One system I worked on recently involved about 20 developer years of effort, and about 40 core years of computation... I'm pretty sure the developers machines combined spent far more energy than the production systems, for a Ruby deployment, before factoring in any other energy use relating to difference in effort. |
|