5 ms·
Things work the same with any resource, not just actual money - it could be team size, or processor cycles and memory bytes. If you free up 200 ms of CPU cycles
by yummypaint 2y ago
Things work the same with any resource, not just actual money - it could be team size, or processor cycles and memory bytes. If you free up 200 ms of CPU cycles and 500 megs of RAM, someone else can deploy their functionality using these newly available resources, and then you won’t be able to. In fact, a mature, well-run CI system will measure everyone’s resource footprint after each commit, and will not let you exceed your budget, which was frozen at some point based on how much you were using at the time (hope it was a lot! - always spend like crazy before the baseline is established!) Is it any wonder that people learn to never optimize their code - unless they want to deploy something new themselves, and only after asking for more resources to deploy it and not getting any?
This explains so much. It also sounds like broken water laws in the western US that incentivise farmers to intentionally waste water to preserve their future ability to waste water.
- darkhorn 2y agoDuring Covid European planes were flying to keep their slots https://www.theguardian.com/environment/2022/jan/26/airlines-flying-near-empty-ghost-flights-to-retain-eu-airport-slots https://www.theguardian.com/environment/2022/jan/26/airlines... Another one is to keep communication satalite slotes. If you loose a slot another country can claim your orbit.
- apantel 2y agoCoordination between more than one developer is the root of all evil.
- throwup238 2y agoThis is what Knuth actually said: > We should forget about our coworkers, say about 97% of the time: premature coordination is the root of all evil. Yet we should not pass up our opportunities in that critical 3% to take credit for their work.
- taneq 2y agoRemember that he's only proven this statement correct, he hasn't actually tested it. ;)
- deleted 2y ago[deleted]
- vbezhenar 2y agoWhy does it happen? My CI launches separate kubernetes pod for every incoming task. If there are not enough servers, autoscaler will spin up new and remove it after some time. So there are not much expenses, we're paying for what we using. I feel that fast CI iterations are very important for developers.
- XorNot 2y agoThis has been the bane of my entire career. I have never, not once, encountered a CI system that could run the test suite faster then my development machine. Which is absurd. Cloud resources on servers with more CPUs then I have, and yet the difference in timing is measured in tens of minutes.
- dilyevsky 2y agoIn most cases i have experienced this phenomenon is caused by the fact that cloud block devices are garbage compared to your machine
- tonyarkles 2y agoAnd often CPU as well if your machine has a reasonable number of cores.
- kevin_nisbet 2y agoThat combined with the scheduling layers... on the CI service the company I'm working for uses it takes like 2 minutes to just start the job.
- Aeolun 2y agoEven creating whole new AWS instances each time it shouldn’t take more than 1m. You can apparently bring it down to 5s by suspending instead of creating instances.
- 2y ago
- mananaysiempre 2y agoNo reason to go that deep. Spending in large bureaucracies (public or private) often works similarly: there’s a lot of hair on fire and throwing money frantically around at the end of a reporting period, because you know if you don’t spend it you’ll get a smaller budget next time. (It was that way at all levels in late Soviet Union, it’s still that way in at least one F100 IT giant.)
- applied_heat 2y agoCanadian government organizations and military also
- exergy 2y agoA (unfortunately still valid) running joke about German public administration is that November is the high season for fax machine sales people
- BeFlatXIII 2y ago> It was that way at all levels in late Soviet Union The inside of most corporations resembles the command economies we were told to fear.