Commit e6f1858b35a85b943f1ca9e63ba112dec42180da
1 parent
ab3392f4
Document carbon footprint evaluation
Showing
2 changed files
with
64 additions
and
0 deletions
doc/source/users/environment.rst
0 → 100755
| 1 | +.. _sec_environment: | |
| 2 | + | |
| 3 | +Environmental impact | |
| 4 | +==================== | |
| 5 | + | |
| 6 | +Like any human activity, using ctools will have an environmental impact. This | |
| 7 | +includes for example the greenhouse gas emissions related to electricity | |
| 8 | +production that is needed to run your computer or data centre. It includes as | |
| 9 | +well the environmental footprint of your computing hardware, the power and | |
| 10 | +material behind your internet connection, your storage array, and even the | |
| 11 | +footprint of the personnel that eventually runs your data centre. | |
| 12 | + | |
| 13 | +As ctools user you should be aware of this footprint, and you should aim | |
| 14 | +to reduce it as much as possible. | |
| 15 | + | |
| 16 | +To guide you in this endeavor, all ctools and cscripts inform you at the end | |
| 17 | +of the log file about the estimated carbon footprint of your computations: | |
| 18 | + | |
| 19 | +.. code-block:: bash | |
| 20 | + | |
| 21 | + 2022-02-18T22:33:26: Application "ctlike" terminated after 3910.0 wall clock seconds, consuming 3881.18 seconds of CPU time and generating a carbon footprint of 3.81083 g eCO2. | |
| 22 | + | |
| 23 | +This estimate is based on the study of | |
| 24 | +`Berthoud et al. (2020) <https://hal.archives-ouvertes.fr/hal-02549565v4/document>`_ | |
| 25 | +who assessed the carbon footprint of the DAHU cluster of the UMS GRICAD (Grenoble, | |
| 26 | +France) in 2019. Their study included | |
| 27 | + | |
| 28 | +* server fabrication | |
| 29 | +* server environment | |
| 30 | +* server usage (electricity) | |
| 31 | +* travelling of personnel in the context of their work | |
| 32 | +* travelling of personnel from home to office | |
| 33 | +* personnel equipment | |
| 34 | +* personnel energy | |
| 35 | + | |
| 36 | +`Berthoud et al. (2020) <https://hal.archives-ouvertes.fr/hal-02549565v4/document>`_ | |
| 37 | +found that, per CPU hour, the footprint of the GRICAD data centre was 2.43 g CO2e | |
| 38 | +(equivalent CO2 emissions) due to electricity use and 2.25 g CO2e due to the data | |
| 39 | +centre environment, hardware fabrication and the personnel. For their study a | |
| 40 | +carbon intensity of 108 g eCO2 / kWh for greenhouse gas emission due to | |
| 41 | +electricity generation was assumed. | |
| 42 | + | |
| 43 | +The latter varies substantially between countries. While the current electricity mix | |
| 44 | +in France has a (rounded) carbon intensity of 60 g eCO2 / kWh, values go through | |
| 45 | +240 g eCO2 / kWh (Spain), 410 g eCO2 / kWh (Italy), 460 g eCO2 / kWh (Germany), | |
| 46 | +520 g eCO2 / kWh (USA), up to 840 g eCO2 / kWh (Australia). So eventually, you should | |
| 47 | +think about doing your computations in a country with a low carbon intensity, or make | |
| 48 | +sure that your data centre is running on a low carbon energy source. | |
| 49 | + | |
| 50 | +ctools will determine in which country your code is executed and fetch the appropriate | |
| 51 | +carbon intensity for the general energy mix in this country to estimate the carbon | |
| 52 | +footprint of your computations. The estimate is done using | |
| 53 | + | |
| 54 | +.. math:: | |
| 55 | + {\rm Carbon\,\,footprint} = \left( 2.25 + 2.43 \frac{\rm CI}{108} \right) \times {\rm CPU\,\,hours} | |
| 56 | + | |
| 57 | +where :math:`{\rm CI}` is the carbon intensity of the electricity mix in your country | |
| 58 | +in units of g eCO2 / kWh, :math:`{\rm CPU\,\,hours}` is the number of CPU hours your | |
| 59 | +computation took, and :math:`{\rm Carbon\,\,footprint}` is the carbon footprint in g eCO2. | |
| 60 | + | |
| 61 | +The carbon footprint of all ctools and cscript runs are stored in an ASCII file | |
| 62 | +that you will find in a folder under your home directory, named ``.gamma/statistics.csv``. | |
| 63 | + | ... | ... |