These Five Tricks Can Make Your Apps Greener, Cheaper, & Nicer

Embed

Start on current slide

Slide 1

Slide 1 text

Holly Cummins Senior Principal Software Engineer, Quarkus ADEO x Decathlon Digital Dev Summit May 27, 2026 these five tricks can make your apps greener cheaper & nicer

Slide 2

Slide 2 text

@holly_cummins #RedHat Sources: https://www.greenit.fr/wp-content/uploads/2019/11/GREENIT_EENM_etude_EN_accessible.pdf https://ourworldindata.org/ghg-emissions-by-sector the digital world creates more carbon emissions than aviation

Slide 3

Slide 3 text

@holly_cummins #RedHat Lighter area represents high and low estimates, where available. Sources: https://www.iea.org/fuels-and-technologies/data-centres-networks https://ourworldindata.org/grapher/electricity-demand?tab=table&country=USA~GBR~FRA~DEU~IND~BRA data centres use as much electricity as a medium country

Slide 4

Slide 4 text

@holly_cummins #RedHat it’s not just artificial intelligence

Slide 5

Slide 5 text

@holly_cummins #RedHat it’s not just artificial intelligence it’s not just cryptocurrency mining

Slide 6

Slide 6 text

@holly_cummins #RedHat it’s not just artificial intelligence it’s not just cryptocurrency mining it’s all of us

Slide 7

Slide 7 text

@holly_cummins #RedHat aaaaaaaargh

Slide 8

Slide 8 text

@holly_cummins #RedHat aaaaaaaargh?

Slide 9

Slide 9 text

@holly_cummins #RedHat we have solutions

Slide 10

Slide 10 text

@holly_cummins #RedHat green software foundation: principles

Slide 11

Slide 11 text

@holly_cummins #RedHat carbon awareness green software foundation: principles

Slide 12

Slide 12 text

@holly_cummins #RedHat carbon awareness green software foundation: principles where

Slide 13

Slide 13 text

@holly_cummins #RedHat carbon awareness green software foundation: principles where when

Slide 14

Slide 14 text

@holly_cummins #RedHat carbon awareness green software foundation: principles hardware efficiency where when

Slide 15

Slide 15 text

@holly_cummins #RedHat carbon awareness green software foundation: principles hardware efficiency where when elasticity

Slide 16

Slide 16 text

@holly_cummins #RedHat carbon awareness green software foundation: principles hardware efficiency where when elasticity utilisation

Slide 17

Slide 17 text

@holly_cummins #RedHat carbon awareness green software foundation: principles hardware efficiency electricity efficiency where when elasticity utilisation

Slide 18

Slide 18 text

@holly_cummins #RedHat algorithms carbon awareness green software foundation: principles hardware efficiency electricity efficiency where when elasticity utilisation

Slide 19

Slide 19 text

@holly_cummins #RedHat algorithms stack carbon awareness green software foundation: principles hardware efficiency electricity efficiency where when elasticity utilisation

Slide 20

Slide 20 text

@holly_cummins #RedHat algorithms stack carbon awareness hardware efficiency electricity efficiency where when elasticity utilisation green software foundation: principles

Slide 21

Slide 21 text

@holly_cummins #RedHat what programming languages create the least carbon? stack

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

@holly_cummins #RedHat

Slide 24

Slide 24 text

energy consumption of programming languages

Slide 25

Slide 25 text

@holly_cummins rust

Slide 26

Slide 26 text

@holly_cummins rust rust is hard

Slide 27

Slide 27 text

@holly_cummins rust trading off human efficiency against machine efficiency rust is hard

Slide 28

Slide 28 text

@holly_cummins java is nice

Slide 29

Slide 29 text

@holly_cummins #RedHat not all java is equally efficient

Slide 30

Slide 30 text

digression: measuring carbon is hard

Slide 31

Slide 31 text

@holly_cummins #RedHat step 1: measure power usage

Slide 32

Slide 32 text

@holly_cummins #RedHat step 1: measure power usage wall power measurement

Slide 33

Slide 33 text

@holly_cummins #RedHat step 1: measure power usage wall power measurement more complete

Slide 34

Slide 34 text

@holly_cummins #RedHat step 1: measure power usage wall power measurement more complete needs access to the wall

Slide 35

Slide 35 text

@holly_cummins #RedHat step 1: measure power usage wall power measurement more complete needs access to the wall RAPL

Slide 36

Slide 36 text

@holly_cummins #RedHat step 1: measure power usage wall power measurement more complete needs access to the wall RAPL programmatically accessible

Slide 37

Slide 37 text

@holly_cummins #RedHat step 1: measure power usage wall power measurement more complete needs access to the wall RAPL programmatically accessible misses some components

Slide 38

Slide 38 text

@holly_cummins #RedHat step 1: measure power usage wall power measurement more complete needs access to the wall data costs carbon RAPL programmatically accessible misses some components

Slide 39

Slide 39 text

@holly_cummins #RedHat

Slide 40

Slide 40 text

@holly_cummins #RedHat

Slide 41

Slide 41 text

@holly_cummins #RedHat

Slide 42

Slide 42 text

@holly_cummins #RedHat load

Slide 43

Slide 43 text

@holly_cummins #RedHat Source: Teads EC2 instances carbon dataset

Slide 44

Slide 44 text

@holly_cummins #RedHat coal wind step 2: convert power usage to carbon solar

Slide 45

Slide 45 text

@holly_cummins #RedHat published energy mixes (these are made-up energy mixes)

Slide 46

Slide 46 text

@holly_cummins #RedHat step 3: embedded carbon (manufacturing has costs)

Slide 47

Slide 47 text

@holly_cummins #RedHat simpler models?

Slide 48

Slide 48 text

@holly_cummins #RedHat all models are wrong, some are useful

Slide 49

Slide 49 text

@holly_cummins #RedHat

Slide 50

Slide 50 text

@holly_cummins #RedHat these two columns are almost the same

Slide 51

Slide 51 text

@holly_cummins #RedHat Energy 1 10 100 Time 1 10 100 energy efficiency across programming languages Python Rust Java Go

Slide 52

Slide 52 text

@holly_cummins #RedHat Energy 1 10 100 Time 1 10 100 the trend line is more or less straight energy efficiency across programming languages Python Rust Java Go

Slide 53

Slide 53 text

@holly_cummins #RedHat energy consumption (sort of, mostly) is proportional to execution time* * assuming hardware and other resource stays the same

Slide 54

Slide 54 text

@holly_cummins #RedHat trick 1: the vrrrrrooooooooom model* * a made-up name

Slide 55

Slide 55 text

@holly_cummins #RedHat trick 1: the vrrrrrooooooooom model* * a made-up name faster software is greener software

Slide 56

Slide 56 text

@holly_cummins

Slide 57

Slide 57 text

@holly_cummins invented by Dr. Vroom (really!)

Slide 58

Slide 58 text

@holly_cummins naming is the hardest problem in computer science invented by Dr. Vroom (really!)

Slide 59

Slide 59 text

@holly_cummins naming is the hardest problem in computer science

Slide 60

Slide 60 text

@holly_cummins

Slide 61

Slide 61 text

@holly_cummins #RedHat not all java is equally fast

Slide 62

Slide 62 text

@holly_cummins #RedHat not all java is equally efficient

Slide 63

Slide 63 text

case study quarkus

Slide 64

Slide 64 text

@holly_cummins #RedHat

Slide 65

Slide 65 text

@holly_cummins #RedHat

Slide 66

Slide 66 text

@holly_cummins #RedHat does being small and fast reduce carbon footprint?

Slide 67

Slide 67 text

#Quarkus @holly_cummins measure, don’t guess.

Slide 68

Slide 68 text

did measurements show quarkus is more efficient?

Slide 69

Slide 69 text

@holly_cummins #RedHat Source: Clement Escoffier cost impact of framework choice Setup: • 800 requests/second, over 20 days • SLA > 99% • AWS instances Assumptions: • Costs are for us-east-1 data centre

Slide 70

Slide 70 text

@holly_cummins #RedHat

Slide 71

Slide 71 text

@holly_cummins #RedHat to measure energy, we would need:

Slide 72

Slide 72 text

@holly_cummins #RedHat to measure energy, we would need: (a) hardware access

Slide 73

Slide 73 text

@holly_cummins #RedHat to measure energy, we would need: (a) hardware access (b) time machine

Slide 74

Slide 74 text

@holly_cummins #RedHat load to measure energy, we would need: (a) hardware access (b) time machine

Slide 75

Slide 75 text

@holly_cummins #RedHat Source: Teads EC2 instances carbon dataset

Slide 76

Slide 76 text

Slide 77

Slide 77 text

@holly_cummins #RedHat cost and carbon impact of framework choice Carbon estimated using TEADS dataset

Slide 78

Slide 78 text

@holly_cummins #RedHat trick 2: the economic model*

Slide 79

Slide 79 text

@holly_cummins #RedHat trick 2: the economic model* * "economic input-output life cycle assessment"

Slide 80

Slide 80 text

@holly_cummins #RedHat reducing your cloud spend (probably) reducing your carbon footprint* hardware spend electricity bill * if you keep other factors the same

Slide 81

Slide 81 text

@holly_cummins #RedHat Setup: • 800 requests/second, over 20 days • SLA > 99% Assumptions: • 50% load • us-east-1 data centre • Teads dataset Source: Clement Escoffier x Teads cloud carbon impact of framework choice

Slide 82

Slide 82 text

Slide 83

Slide 83 text

@holly_cummins #RedHat what if we measure on-prem?

Slide 84

Slide 84 text

@holly_cummins #RedHat Setup: • REST + CRUD • large heap • RAPL energy measurement • multiple instances to support high load Assumptions: • US energy mix Source: John O’Hara carbon as a function of load

Slide 85

Slide 85 text

Slide 86

Slide 86 text

Slide 87

Slide 87 text

@holly_cummins #RedHat capacity Source: John O’Hara Setup: • REST + CRUD • large heap • RAPL energy measurement Assumptions: • US energy mix carbon as a function of load (single instance)

Slide 88

Slide 88 text

Slide 89

Slide 89 text

@holly_cummins #RedHat capacity Source: John O’Hara Setup: • REST + CRUD • large heap • RAPL energy measurement Assumptions: • US energy mix carbon as a function of load (single instance) shorter line means lower max throughput higher line means worse carbon footprint

Slide 90

Slide 90 text

@holly_cummins #RedHat capacity Source: John O’Hara Setup: • REST + CRUD • large heap • RAPL energy measurement Assumptions: • US energy mix carbon as a function of load (single instance) vrrrooom model in action: quarkus on JVM has the smallest footprint … because it has the highest throughput shorter line means lower max throughput higher line means worse carbon footprint

Slide 91

Slide 91 text

@holly_cummins #RedHat trick 3: use quarkus

Slide 92

Slide 92 text

@holly_cummins #RedHat trick 3: use quarkus quarkus ‘automatically’ saves

Slide 93

Slide 93 text

@holly_cummins #RedHat trick 3: use quarkus quarkus ‘automatically’ saves • time

Slide 94

Slide 94 text

@holly_cummins #RedHat trick 3: use quarkus quarkus ‘automatically’ saves • time • money

Slide 95

Slide 95 text

@holly_cummins #RedHat trick 3: use quarkus quarkus ‘automatically’ saves • time • money • carbon (~2x)

Slide 96

Slide 96 text

@holly_cummins #RedHat trick 3: use quarkus quarkus ‘automatically’ saves • time • money • carbon (~2x) • … even when Spring compatibility libraries are used (almost no code changes except dependencies and tests)

Slide 97

Slide 97 text

Slide 98

Slide 98 text

@holly_cummins #RedHat low load choose quarkus native normal load choose quarkus on jvm

Slide 99

Slide 99 text

@holly_cummins #RedHat carbon awareness green software foundation: principles hardware efficiency electricity efficiency

Slide 100

Slide 100 text

@holly_cummins #RedHat carbon awareness green software foundation: principles hardware efficiency electricity efficiency elasticity

Slide 101

Slide 101 text

@holly_cummins #RedHat carbon awareness green software foundation: principles hardware efficiency electricity efficiency elasticity utilisation

Slide 102

Slide 102 text

@holly_cummins #RedHat application utilisation

Slide 103

Slide 103 text

@holly_cummins #RedHat application utilisation high utilisation good case

Slide 104

Slide 104 text

@holly_cummins #RedHat application utilisation over-utilisation very bad case

Slide 105

Slide 105 text

@holly_cummins #RedHat application utilisation over-utilisation very bad case under-utilisation wasteful case

Slide 106

Slide 106 text

@holly_cummins #RedHat application elasticity high utilisation good case @holly_cummins

Slide 107

Slide 107 text

@holly_cummins #RedHat application elasticity scale-up good utilisation @holly_cummins

Slide 108

Slide 108 text

@holly_cummins #RedHat application elasticity scale-down good utilisation @holly_cummins

Slide 109

Slide 109 text

@holly_cummins #RedHat native quarkus is great at elasticity: starts faster than a light bulb

Slide 110

Slide 110 text

@holly_cummins #RedHat … but elasticity isn’t just a technical problem

Slide 111

Slide 111 text

#RedHat @hollycummins.com Hey boss, I created a Kubernetes cluster. 2018

Slide 112

Slide 112 text

#RedHat @hollycummins.com Hey boss, I created a Kubernetes cluster. I forgot it for 2 months. 2018

Slide 113

Slide 113 text

#RedHat @hollycummins.com Hey boss, I created a Kubernetes cluster. I forgot it for 2 months. … and it’s €1000 a month. 2018

Slide 114

Slide 114 text

#RedHat @hollycummins.com

Slide 115

Slide 115 text

#RedHat @holly_cummins 2017 server-survey 25% doing no useful work (16,000 sampled)

Slide 116

Slide 116 text

#RedHat @holly_cummins 2017 server-survey 25% doing no useful work (16,000 sampled) “perhaps someone forgot to turn them off”

Slide 117

Slide 117 text

#RedHat @[email protected] https://www.anthesisgroup.com/wp-content/uploads/2019/11/Comatose-Servers-Redux-2017.pdf 2014 server-survey 29% active less than 5% of the time (4,000 sampled)

Slide 118

Slide 118 text

@holly_cummins #RedHat cloud elasticity? https://www.business2community.com/cloud-computing/overprovisioning-always-on-resources-lead-to-26-6-billion-in-public-cloud-waste-expected-in-2021-02381033

Slide 119

Slide 119 text

@holly_cummins #RedHat cloud elasticity? 2021: https://www.business2community.com/cloud-computing/overprovisioning-always-on-resources-lead-to-26-6-billion-in-public-cloud-waste-expected-in-2021-02381033

Slide 120

Slide 120 text

@holly_cummins #RedHat cloud elasticity? 2021: $26.6 billion wasted https://www.business2community.com/cloud-computing/overprovisioning-always-on-resources-lead-to-26-6-billion-in-public-cloud-waste-expected-in-2021-02381033

Slide 121

Slide 121 text

@holly_cummins #RedHat cloud elasticity? 2021: $26.6 billion wasted by always-on cloud instances https://www.business2community.com/cloud-computing/overprovisioning-always-on-resources-lead-to-26-6-billion-in-public-cloud-waste-expected-in-2021-02381033

Slide 122

Slide 122 text

@holly_cummins #RedHat it’s not just money

Slide 123

Slide 123 text

@holly_cummins #RedHat it’s not just electricity it’s not just money

Slide 124

Slide 124 text

@holly_cummins #RedHat it’s not just electricity it’s water it’s not just money

Slide 125

Slide 125 text

@holly_cummins #RedHat it’s not just electricity it’s water it’s e-waste it’s not just money

Slide 126

Slide 126 text

#RedHat @hollycummins.com shutting systems off can seem scary

Slide 127

Slide 127 text

@hollycummins.com #RedHat ultimate elasticity

Slide 128

Slide 128 text

#RedHat @hollycummins.com we don’t switch the light off because we’re not sure if it will come back on never happens

Slide 129

Slide 129 text

#RedHat @hollycummins.com we don’t switch the server off because we’re not sure if it will come back on happens all the time

Slide 130

Slide 130 text

#RedHat @hollycummins.com we don’t switch the light off because it’s so much effort to turn it back on never happens

Slide 131

Slide 131 text

#RedHat @hollycummins.com we don’t switch the server off because it would be too much work to recreate it happens all the time

Slide 132

Slide 132 text

#RedHat @hollycummins.com we don’t switch the server off because we’re not really sure if it we’re using it happens all the time

Slide 133

Slide 133 text

@holly_cummins #RedHat what if … turning applications off was no more scary than turning the lights off? ultimate elasticity

Slide 134

Slide 134 text

@holly_cummins #RedHat

Slide 135

Slide 135 text

@holly_cummins #RedHat

Slide 136

Slide 136 text

@holly_cummins #RedHat turning it off and on again must

Slide 137

Slide 137 text

@holly_cummins #RedHat turning it off and on again must • be fast

Slide 138

Slide 138 text

@holly_cummins #RedHat turning it off and on again must • be fast • actually work

Slide 139

Slide 139 text

@holly_cummins #RedHat turning it off and on again must • be fast • actually work • idempotency

Slide 140

Slide 140 text

@holly_cummins #RedHat turning it off and on again must • be fast • actually work • idempotency • resiliency

Slide 141

Slide 141 text

@holly_cummins #RedHat architect things to be turned off and on often

Slide 142

Slide 142 text

@holly_cummins #RedHat trick 4: LightSwitchOps architect things to be turned off and on often

Slide 143

Slide 143 text

@holly_cummins #RedHat trick 4: LightSwitchOps architect things to be turned off and on often

Slide 144

Slide 144 text

@hollycummins.com #RedHat step 1: no more scary state

Slide 145

Slide 145 text

#RedHat @hollycummins.com GitOps (infrastructure as code)

Slide 146

Slide 146 text

#RedHat @hollycummins.com GitOps (infrastructure as code)

Slide 147

Slide 147 text

#RedHat @hollycummins.com

Slide 148

Slide 148 text

#RedHat @hollycummins.com spin it down

Slide 149

Slide 149 text

#RedHat @hollycummins.com kubectl apply -f all-my-cluster/ spin it down spin it up

Slide 150

Slide 150 text

#RedHat @hollycummins.com kubectl apply -f all-my-cluster/ spin it down spin it up

Slide 151

Slide 151 text

#RedHat @hollycummins.com kubectl apply -f all-my-cluster/ ansible-playbook stuff.yml spin it down spin it up

Slide 152

Slide 152 text

@hollycummins.com #RedHat step 1: no more scary state step 2: automate, automate

Slide 153

Slide 153 text

#RedHat @hollycummins.com large UK bank, 2013 50% reduction in CPUs with a lease system self-destructing instances

Slide 154

Slide 154 text

@holly_cummins #RedHat scripting we used to leave our applications running all the time when we scripted turning them off at night, we reduced our cloud bill by 30% @darkandnerdy, Chicago DevOpsDays

Slide 155

Slide 155 text

@holly_cummins #RedHat

Slide 156

Slide 156 text

@holly_cummins #RedHat

Slide 157

Slide 157 text

@holly_cummins #RedHat

Slide 158

Slide 158 text

@holly_cummins #RedHat quarkus!

Slide 159

Slide 159 text

#RedHat @hollycummins.com all the —opses

Slide 160

Slide 160 text

#RedHat @hollycummins.com GreenOps

Slide 161

Slide 161 text

#RedHat @hollycummins.com GreenOps greenops is a mid-sized trilobite (really)

Slide 162

Slide 162 text

@holly_cummins #RedHat FinOps figuring out who in your company forgot to turn off their cloud

Slide 163

Slide 163 text

#Quarkus @holly_cummins you can’t optimise what you can’t measure

Slide 164

Slide 164 text

@holly_cummins #RedHat

Slide 165

Slide 165 text

@holly_cummins #RedHat backstage.io

Slide 166

Slide 166 text

@holly_cummins #RedHat backstage.io •cost insights plugin

Slide 167

Slide 167 text

@holly_cummins #RedHat backstage.io •cost insights plugin •cloud carbon footprint plugin

Slide 168

Slide 168 text

@holly_cummins #RedHat algorithms stack carbon awareness hardware efficiency electricity efficiency where when elasticity utilisation green software foundation: principles

Slide 169

Slide 169 text

trick 5: electricity source

Slide 170

Slide 170 text

not all energy is equal

Slide 171

Slide 171 text

@holly_cummins #RedHat data center location matters

Slide 172

Slide 172 text

@holly_cummins #RedHat

Slide 173

Slide 173 text

@holly_cummins #RedHat

Slide 174

Slide 174 text

@holly_cummins #RedHat we need to talk about virginia

Slide 175

Slide 175 text

@holly_cummins #RedHat look at the sustainability information before choosing a hosting region

Slide 176

Slide 176 text

@holly_cummins #RedHat look at the sustainability information before choosing a hosting region choose a cloud provider who make this easy

Slide 177

Slide 177 text

@holly_cummins #RedHat time of day matters • (most) renewables are intermittent • if grid load is high, shortfalls are filled by fossil fuels

Slide 178

Slide 178 text

@holly_cummins #RedHat what about the ai-lephant in the room?

Slide 179

Slide 179 text

@holly_cummins #RedHat

Slide 180

Slide 180 text

@holly_cummins #RedHat tokenmaxxing

Slide 181

Slide 181 text

@holly_cummins #RedHat ai trick i do not add “destroy planet” to your targets

Slide 182

Slide 182 text

@holly_cummins #RedHat ai trick i do not add “destroy planet” to your targets

Slide 183

Slide 183 text

@holly_cummins #RedHat ai trick ii don’t use a bigger model than you need

Slide 184

Slide 184 text

@holly_cummins #RedHat remember the vrrrrrooooooooom model?

Slide 185

Slide 185 text

@holly_cummins #RedHat remember the vrrrrrooooooooom model? faster software is greener software

Slide 186

Slide 186 text

@holly_cummins #RedHat bigger models are slower

Slide 187

Slide 187 text

@holly_cummins #RedHat 1.3 - 2.2x faster https://www.reddit.com/r/ClaudeAI/comments/1r9jf2j/i_benchmarked_opus_46_vs_sonnet_46_on_agentic_pr/ claude sonnet is than opus

Slide 188

Slide 188 text

@holly_cummins #RedHat ai trick ii don’t use a more expensive model than you need

Slide 189

Slide 189 text

@holly_cummins #RedHat ai trick ii don’t use a more expensive model than you need

Slide 190

Slide 190 text

@holly_cummins #RedHat reminder: economic model

Slide 191

Slide 191 text

@holly_cummins #RedHat reducing your token spend (probably) reducing your carbon footprint* subscription level * if you keep other factors the same

Slide 192

Slide 192 text

@holly_cummins #RedHat 1.7 - 5.5x costlier https://www.reddit.com/r/ClaudeAI/comments/1r9jf2j/i_benchmarked_opus_46_vs_sonnet_46_on_agentic_pr/ claude sonnet is than opus

Slide 193

Slide 193 text

@holly_cummins #RedHat 10 - 50x cheaper https://www.reddit.com/r/ClaudeAI/comments/1r9jf2j/i_benchmarked_opus_46_vs_sonnet_46_on_agentic_pr/ deep seek is for a small* quality drop

Slide 194

Slide 194 text

@holly_cummins #RedHat ai trick iii don’t route trivial commands through an LLM

Slide 195

Slide 195 text

@holly_cummins #RedHat

Slide 196

Slide 196 text

@holly_cummins #RedHat

Slide 197

Slide 197 text

@holly_cummins #RedHat

Slide 198

Slide 198 text

@holly_cummins #RedHat ai trick iv offload to deterministic tools

Slide 199

Slide 199 text

@holly_cummins #RedHat 1. Create the project using quarkus_create with the extensions above. This will auto-start dev mode with a PostgreSQL Dev Service (no manual DB setup needed). │ │ 2. Load extension skills via quarkus_skills to learn the correct patterns for REST and Panache. │ │ 3. Verify the app starts successfully and the generated starter endpoints work by checking the dev mode logs. │ │ │ │ Verification │ │ │ │ - Confirm dev mode starts without errors │ │ - Confirm PostgreSQL Dev Service is running (auto-provisioned by Quarkus) │ │ - Test the generated starter endpoint(s) via curl or the Dev UI ❯ /usage Total duration (API): 58s Total duration (wall): 2m 39s Total code changes: 34 lines added, 0 lines removed Usage by model: claude-opus-4-6: 2.3k input, 2.6k output, 160.7k cache read, 44.7k cache write ($0.4364) 10x generating a quarkus app cheaper with quarkus mcp

Slide 200

Slide 200 text

@holly_cummins #RedHat like using a lamborghini to mow the lawn

Slide 201

Slide 201 text

@holly_cummins #RedHat ai trick iv time of day matters location matters

Slide 202

Slide 202 text

@holly_cummins #RedHat ai trick iv time of day matters location matters

Slide 203

Slide 203 text

@holly_cummins #RedHat aaaaaaaargh?

Slide 204

Slide 204 text

@holly_cummins #RedHat efficient software:

Slide 205

Slide 205 text

@holly_cummins #RedHat software that does less of what you don’t need efficient software:

Slide 206

Slide 206 text

@holly_cummins #RedHat efficient software:

Slide 207

Slide 207 text

@holly_cummins #RedHat software that does what you need using fewer resources efficient software:

Slide 208

Slide 208 text

@holly_cummins #RedHat “no-regrets” solutions

Slide 209

Slide 209 text

@holly_cummins #RedHat

Slide 210

Slide 210 text

@holly_cummins #RedHat co-benefits

Slide 211

Slide 211 text

@holly_cummins #RedHat co-benefits the double win

Slide 212

Slide 212 text

@holly_cummins #RedHat co-benefits the double win win-win

Slide 213

Slide 213 text

@holly_cummins #RedHat co-benefits the double win win-win twofer

Slide 214

Slide 214 text

@holly_cummins #RedHat co-benefits the double win win-win twofer überwinden

Slide 215

Slide 215 text

@holly_cummins #RedHat co-benefits the double win win-win twofer überwinden

Slide 216

Slide 216 text

@holly_cummins #RedHat climate solutions can make everything better

Slide 217

Slide 217 text

@holly_cummins #RedHat the double-win turning things off saves a lot of money

Slide 218

Slide 218 text

@holly_cummins #RedHat the double-win solar power can be really inexpensive

Slide 219

Slide 219 text

@holly_cummins #RedHat remember the zombie servers? https://www.business2community.com/cloud-computing/overprovisioning-always-on-resources-lead-to-26-6-billion-in-public-cloud-waste-expected-in-2021-02381033

Slide 220

Slide 220 text

@holly_cummins #RedHat remember the zombie servers? what else could we do with that $26.6 billion of wasted cloud spend? https://www.business2community.com/cloud-computing/overprovisioning-always-on-resources-lead-to-26-6-billion-in-public-cloud-waste-expected-in-2021-02381033

Slide 221

Slide 221 text

@holly_cummins #RedHat remember the vrrrrrooooooooom model? (probably not, it was a made-up name)

Slide 222

Slide 222 text

@holly_cummins #RedHat the double-win

Slide 223

Slide 223 text

@holly_cummins #RedHat the double-win

Slide 224

Slide 224 text

@holly_cummins #RedHat “this is not sacrifice. it’s advancement.” – Dr. Jonathan Foley

Slide 225

Slide 225 text

@holly_cummins #RedHat tl;dpa (too long; didn’t pay attention) trick 1: the vrrrooooom model says faster is greener trick 2: the economic model says cheaper is greener trick 3: choose a fast and energy-efficient framework (such as quarkus) trick 4: architect to be able to turn stuff off (LightSwitchOps) trick 5: choose your time of day and hosting wisely