Holy crap
Holy crap
You have: 40 MWh
You want: tonoil
* 3.4393809
/ 0.29075
You have: 1 tonoil
You want: barreloil
* 6.8419323
/ 0.14615754
You have: 6.84 barrel
You want: liter
* 1087.4731
/ 0.00091956298
So, roughly 1,100 litres of oil per 40 MWh(thermal).The generator is likely ~30% efficient at converting heat to eletricity, so bump that up to 3,700 litres/hour.
Even allowing for other inefficiencies, 12,000 litre/hr seems high to me. Though as a practical measure it may be correct. It's within a factor of 4 of the actual demand though.
(Calculations using GNU units.)
Corrected:
You have: 40 MWh
You want: tonoil
* 3.4393809
/ 0.29075
You have: 3.439 tonoil
You want: barreloil
* 23.529405
/ 0.042500012
You have: 23.529 barrel
You want: liter
* 3740.8121
/ 0.00026732164
You have: 3740/30%
You want:
Definition: 12466.667
Or a bit above 12,000 litres. Article was correct. You have: 40 MW/30% / (10722.2 W*hr/L)
You want: L/hr
40 MW/30% / (10722.2 W*hr/L) = 12435.259 L/hr literoil = 1 barreloil * liter/barrel
And the calculation gives me ...10.69 kWh/LThe barreloil value is for crude, diesel may have a slightly higher net energy density. But we're good to 3 sig figs.
I could have bypassed the tonoil step and calculated thermal energy in barreloil directly though saving another conversion.
Otherwise I'd have to remember energy density/L of diesel fuel.
I've added the definitions for litre, pound, and kg oil and can now run:
$ units --terse '40 MWh/30%' literoil
12470.969
The fun part though, at least for me, is showing how to do conversions with GNU units, and the equivalences which become apparent doing so. You have: 1 diesel
You want: Wh/L
1 diesel = 10103.465 Wh/L
Slightly different value than in Wikipedia, but close enough.TIL, there are!
Thanks.
(For the curious, the definitions file is ~7500 lines, there's a lot in there. GNU version. For those on MacOS, the stock BSD units offers far less.)
12k liters per hour for the datacenter sounds about right, after accounting for diesel engine efficiency.
[1] https://www.sustainabilityexchange.ac.uk/files/cambridge_reg...
(It's not going to be diesel, it's mostly a mix of coal and natgas depending on where it happens, but that gives you an idea of the size)
So bitcoin is equivalent to 425 Emma Mærsks going full bore continually.
That'd be 6.3 million TEU - which interesting means that for those big ships, a liter of fuel moves one TEU for one hour.
That's a great little number, and actually feels very efficient!
Trains come in third, but they use more fuel.
https://en.wikipedia.org/wiki/Rotor_ship#/media/File:Norsepo...
Those humans would also only use 1/6th as much energy (when assuming around 9.2m Calorie per liter of diesel). So the energy used by that engine could also "run" a million humans. Whatever that ship is carrying, it might be more energy efficient to let people carry it...
Burning through four liters of diesel a second/a bathtub a minute is insane.
I'm a bit tired, but I hope I got that math about right.
Also note that bitcoin miners that have a choice of where to locate choose regions where electricity is cheap, such as those serviced by hydro plants..."most" is a slight stretch, "about half" would probably be more correct - but yeah, it's not good.
I've also heard machine learning training is done in places with cheap energy because the training isn't usually latency-sensitive (querying the trained model might be). Not all AI magic is equally useful, but translation engines are the example I heard of and that's definitely helping me a ton (works better than google translate) as a foreigner in Germany.
How many VMs does an average business actually require, assuming the software wasn't written like total ass?
Carbon output of a diesel generator is horrific compared to just about any form of large scale energy production.
If people were ready to pay some upfront costs, it would be possible to lower long-term costs, but that's CAPEX vs OPEX decision that is not in the hands of the software developers.
Basic profiling can often find bottlenecks that are easy to fix, usually just a result of a simple oversight.
No one is asking for every piece of software to be rewritten in Assembly whilst taking advantage of every possible algorithmic improvement.
But it requires already scarce developers to spend even more time on one task. Those same developers which aready have two missed deadlines in their task queue. What should be done is always nice, but typically doesn't match reality.