Zero Waste, Radical Magic, and Italian Graft – Quarkus Efficiency Secrets

Holly Cummins QCon London April 9, 2024 Zero Waste, Radical
Magic and Italian Graft Quarkus Efficiency Secrets

@holly_cummins Rust

@holly_cummins Q: Is Rust efficient?

@holly_cummins Q: Is Rust efficient? A: Yes, very. Obviously.

@holly_cummins

@holly_cummins Rust is too hard to learn

@holly_cummins

@holly_cummins too difficult to be widely adopted

@holly_cummins

@holly_cummins approach with trepidation

@holly_cummins approach with trepidation notoriously difficult learning curve

@holly_cummins “Rust is the hardest programming language up to that
time I’ve met.” -Michael Vaner https://vorner.github.io/difficult.html

@holly_cummins Rust has no garbage collection. (Sort of.)

@holly_cummins Rust has no garbage collection. (Sort of.) What happens
if we give Rust GC?

@holly_cummins #RedHat

@holly_cummins #RedHat more likely to complete the task required only
about a third as much time

@holly_cummins #RedHat Oh. Maybe Rust isn’t efficient.

@holly_cummins Rust human efficiency machine efficiency

@holly_cummins can we do better? #RedHat

@holly_cummins #RedHat can we do better?

@holly_cummins Enter … Quarkus. #RedHat A Java framework that gets
you going faster, faster. can we do better?

Quarkus applications start fast Quarkus + graalvm 0.014 Seconds REST
application Quarkus + open jdk 0.75 Seconds traditional cloud-native stack 4.3 Seconds https://Quarkus.io/blog/runtime-performance/

@holly_cummins machine Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus
Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus container orchestration machine traditional cloud-native java stack traditional cloud-native java stack traditional cloud-native java stack traditional cloud-native java stack Quarkus applications have high deployment density. Quarkus native

@holly_cummins machine Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus
Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus container orchestration machine traditional cloud-native java stack traditional cloud-native java stack traditional cloud-native java stack traditional cloud-native java stack Quarkus applications have high deployment density. Quarkus native (but Quarkus on JVM is also way smaller than traditional java)

@holly_cummins traditional cloud-native java stack traditional cloud-native java stack traditional
cloud-native java stack traditional cloud-native java stack node.js node.js node.js node.js node.js node.js node.js go go machine go go go go go go go go go go go go go go go go go go go Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus Quarkus … and not just when comparing to other Java frameworks container orchestration machine machine machine https:/ /developers.redhat.com/blog/2017/03/14/java-inside-docker/

Let’s talk about throughput. https://www.redhat.com/en/resources/mi-quarkus-lab-validation-idc-analyst-paper 48 concurrent connections Traditional cloud
native stack 3555 req/s

Let’s talk about throughput. quarkus native 3212 req/s https://www.redhat.com/en/resources/mi-quarkus-lab-validation-idc-analyst-paper 48
concurrent connections Traditional cloud native stack 3555 req/s

Let’s talk about throughput. quarkus native 3212 req/s https://www.redhat.com/en/resources/mi-quarkus-lab-validation-idc-analyst-paper a
trade-off of throughput against footprint 48 concurrent connections Traditional cloud native stack 3555 req/s

@holly_cummins Native compilation trade-offs throughput startup time + footprint

@holly_cummins this is a classic tradeoff

but … traditional cloud native stack 3555 req/s quarkus native
3212 req/s https://www.redhat.com/en/resources/mi-quarkus-lab-validation-idc-analyst-paper a trade-off of throughput against footprint 48 concurrent connections

but … traditional cloud native stack 3555 req/s quarkus on
jvm 6389 req/s quarkus native 3212 req/s https://www.redhat.com/en/resources/mi-quarkus-lab-validation-idc-analyst-paper a trade-off of throughput against footprint 48 concurrent connections

but … traditional cloud native stack 3555 req/s quarkus on
jvm 6389 req/s quarkus native 3212 req/s https://www.redhat.com/en/resources/mi-quarkus-lab-validation-idc-analyst-paper no trade-off, just better :) a trade-off of throughput against footprint 48 concurrent connections

@holly_cummins we beat the trade-off. throughput startup time + footprint

@holly_cummins we beat the trade-off. throughput startup time + footprint
it’s a double-win.

@holly_cummins what’s the secret?

@holly_cummins what’s the secret? what are the secrets?

@holly_cummins Challenge assumptions. African wild ass

@holly_cummins Challenge assumptions. Challenge outdated assumptions. African wild ass

@holly_cummins ssssshhhhhhhh! it’s a secret! Don’t be dynamic.

@holly_cummins ssssshhhhhhhh! it’s a secret! Don’t be dynamic. (Wait, what??)

@holly_cummins dynamic “on-demand”

@holly_cummins dynamic “on-demand” dynamic is better than some alternatives, but
it is not the most efficient

@holly_cummins dynamic “on-demand” dynamic is better than some alternatives, but
it is not the most efficient some unlearning needed

@holly_cummins #RedHat old Java frameworks were optimised for …

@holly_cummins #RedHat long-lived processes old Java frameworks were optimised for
…

@holly_cummins #RedHat long-lived processes annual (!) deployments old Java frameworks
were optimised for …

@holly_cummins #RedHat long-lived processes annual (!) deployments late-binding old Java
frameworks were optimised for …

@holly_cummins #RedHat long-lived processes annual (!) deployments late-binding re-configurable without
restart old Java frameworks were optimised for …

@holly_cummins #RedHat application frameworks were optimised for dynamism

@holly_cummins #RedHat application frameworks were optimised for dynamism dynamism has
a cost

@holly_cummins #RedHat cloud apps are immutable now

@holly_cummins #RedHat a highly dynamic runtime in a container is
pointless

@holly_cummins Java dynamism

@holly_cummins Java dynamism build time

@holly_cummins Java dynamism build time runtime

@holly_cummins Java dynamism packaging (maven, gradle…) build time runtime

@holly_cummins Java dynamism build time runtime

@holly_cummins Java dynamism </> build time runtime load and parse
• config files • properties • yaml • xml • etc.

@holly_cummins Java dynamism </> build time runtime

@holly_cummins Java dynamism @ @ </> build time runtime •
classpath scanning and annotation discovery • attempt to load class to enable/disable features

@holly_cummins Java dynamism @ @ </> build time runtime

@holly_cummins Java dynamism @ @ </> build time runtime build
a metamodel of the world

@holly_cummins Java dynamism @ @ </> build time runtime

@holly_cummins Java dynamism @ @ </> build time runtime start
• thread pools • I/O • etc.

@holly_cummins Java dynamism @ @ </> build time runtime ready
to do work!

@holly_cummins what if we start the application more than once?
@ @ </>

@ @ </> @ @ </>

@ @ </> @ @ </> @ @ </>

@ @ </> @ @ </> @ @ </> @ @ </>

@ @ </> @ @ </> @ @ </> @ @ </> so much work gets redone every time

@holly_cummins Hibernate speed example: JTA auto-wiring

@holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”);

@holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”);

@holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”);

@holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); …

@holly_cummins Hibernate speed example: JTA auto-wiring Class.forName(“LikelyJTAImplementation”); Class.forName(“APossibleJTAImplementation”); Class.forName(“AnotherJTAImplementation”); Class.forName(“NicheJTAImplementation”);
…

Class.forName(“VeryNicheJTAImplementation”); …

Class.forName(“VeryNicheJTAImplementation”); … ~129 auto-wiring attempts

Class.forName(“VeryNicheJTAImplementation”); … ~129 auto-wiring attempts every single start.

@holly_cummins it’s not just JTA this happens for lots of
internal service bindings

@holly_cummins JVM footprint example: Hibernate

@holly_cummins JVM spends time loading classes for specific databases JVM
class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database footprint example: Hibernate

class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database class for unused database turns out they’re never used footprint example: Hibernate

turns out they’re never used JIT spends time unloading classes footprint example: Hibernate

@holly_cummins Hibernate example: ~500 classes which are only useful if
you're running an Oracle database loaded and then unloaded

@holly_cummins Hibernate example: ~500 classes which are only useful if
you're running an Oracle database loaded and then unloaded every single start.

@holly_cummins the true cost of loaded classes isn’t just memory
+ start time

+ start time method dispatching:

@holly_cummins interface the true cost of loaded classes isn’t just
memory + start time method dispatching:

@holly_cummins unused implementation the one we want interface unused implementation
unused implementation the true cost of loaded classes isn’t just memory + start time method dispatching:

@holly_cummins unused implementation the one we want interface megamorphic call
slow dispatching unused implementation unused implementation the true cost of loaded classes isn’t just memory + start time method dispatching:

+ start time the one we want interface

+ start time the one we want monomorphic call fast dispatching interface

@holly_cummins how do we fix all this?

@holly_cummins @ @ </> build time runtime what if we
initialize at build time?

@holly_cummins @ @ </> build time runtime start • thread
pools • I/O • etc. what if we initialize at build time?

@holly_cummins @ @ </> build time runtime ready to do
work! start • thread pools • I/O • etc. what if we initialize at build time?

@holly_cummins @ @ </> repeated starts are now efficient

@holly_cummins @ @ </> repeated starts are now efficient less
wasted work

@holly_cummins the Quarkus way enables native compilation native (graalvm) @
@ </> jvm build time

@holly_cummins

@holly_cummins doing more up-front

@holly_cummins doing more up-front - speeds up start

@holly_cummins doing more up-front - speeds up start - shrinks
memory footprint

@holly_cummins doing more up-front - speeds up start - shrinks
memory footprint - improves throughput (!)

@holly_cummins implementation corollary: libraries must participate in the build process,
not just the runtime process

@holly_cummins implementation corollary: libraries must participate in the build process,
not just the runtime process you need an extensible build process

@holly_cummins ssssshhhhhhhh! it’s a secret! have the right plug-points, so
the whole ecosystem can become faster

@holly_cummins build steps + build items extensible builds

@holly_cummins build steps + build items extensible builds any extension
can make

@holly_cummins #Quarkus #RedHat

@holly_cummins #Quarkus #RedHat build steps

@holly_cummins #Quarkus #RedHat build items

@holly_cummins #Quarkus #RedHat framework automatically determines correct execution order and
injects parameters

@holly_cummins #Quarkus #RedHat build items are communication mechanism between build
steps framework automatically determines correct execution order and injects parameters

@holly_cummins isn’t long compilation kind of terrible for developers? @
@ </>

@holly_cummins isn’t long compilation kind of terrible for developers? not
if you have live coding :) @ @ </>

@holly_cummins framework works out required level of reload live coding

@holly_cummins file reload live coding

@holly_cummins file reload live coding SASS changes detected, will rebuild:
[META-INF/ resources/public/stylesheets/live.scss] Files changed but restart not needed - notified extensions in: 0.043s

@holly_cummins file reload JVM agent reload live coding

@holly_cummins file reload JVM agent reload live coding Application restart
not required, replacing classes via instrumentation Live reload performed via instrumentation, no restart needed, total time: 0.180s

@holly_cummins full restart file reload JVM agent reload live coding

@holly_cummins full restart file reload JVM agent reload live coding
Restarting Quarkus due to changes in Application$RenardeRequest.class, Application.class, Application$ApplicationGlobals.class, Application$Templates.class. Live reload total time: 1.415s

@holly_cummins full restart file reload JVM agent reload not noticeable
(Quarkus starts fast) live coding Restarting Quarkus due to changes in Application$RenardeRequest.class, Application.class, Application$ApplicationGlobals.class, Application$Templates.class. Live reload total time: 1.415s

@holly_cummins fast start enables live coding

@holly_cummins the most expensive resource: humans

@holly_cummins how to make people efficient

@holly_cummins how to make people efficient - make it hard
to get wrong

to get wrong - strong typing

to get wrong - strong typing - garbage collection

to get wrong - strong typing - garbage collection - give them a tight feedback loop

to get wrong - strong typing - garbage collection - give them a tight feedback loop - for manual testing - for automated testing

to get wrong - strong typing - garbage collection - give them a tight feedback loop - for manual testing - for automated testing - allow less typing

to get wrong - strong typing - garbage collection - give them a tight feedback loop - for manual testing - for automated testing - allow less typing thank you, Java - strong typing - garbage collection

to get wrong - strong typing - garbage collection - give them a tight feedback loop - for manual testing - for automated testing - allow less typing thank you, Java - strong typing - garbage collection we just covered this

@holly_cummins developer joy

@holly_cummins ssssshhhhhhhh! it’s a secret! index, index, index (and let
your ecosystem use the index)

@holly_cummins most frameworks need to…

@holly_cummins most frameworks need to… -find all classes + interfaces
+ methods + fields annotated with @X

+ methods + fields annotated with @X -find all classes implementing or extending X

+ methods + fields annotated with @X -find all classes implementing or extending X Java doesn’t help us nothing in the reflection package does this

@holly_cummins Jandex

@holly_cummins Jandex “offline reflection”

@holly_cummins we have an index now what?

@holly_cummins challenge assumptions.

@holly_cummins challenge assumptions. what if developers didn’t have to …
?

@holly_cummins #RedHat package com.example; import org.jboss.logging.Logger; public class Thing {
private static final Logger log = Logger.getLogger(Thing.class); public void doSomething() { log.info("It works!"); } } example: logging

@holly_cummins #RedHat package com.example; import org.jboss.logging.Logger; public class Thing {
private static final Logger log = Logger.getLogger(Thing.class); public void doSomething() { log.info("It works!"); } } example: logging import io.quarkus.logging.Log; Log

@holly_cummins ssssshhhhhhhh! it’s a secret!

@holly_cummins ssssshhhhhhhh! it’s a secret! don’t make humans tell the
computer what the computer already knows

@holly_cummins “but isn’t that dynamism expensive?”

@holly_cummins no. “but isn’t that dynamism expensive?”

@holly_cummins no. - use Jandex to find use-sites of the
Log class “but isn’t that dynamism expensive?”

Log class - inject a static logger field $logger “but isn’t that dynamism expensive?”

Log class - inject a static logger field $logger - replace all calls of Log.method with calls to $logger.method “but isn’t that dynamism expensive?”

Log class - inject a static logger field $logger - replace all calls of Log.method with calls to $logger.method … all at build time “but isn’t that dynamism expensive?”

@holly_cummins logging: compiled version public class MyService { // injected
private static Logger $logger = Logger.getLogger(Thing.class) public void doSomething() { $logger.info(“It works!”); } }

@holly_cummins what if… you could inherit boilerplate Hibernate queries from
a superclass, instead of having to write them all? example: hibernate

@holly_cummins #RedHat @ApplicationScoped public class GreetingRepository { public Entity findByName(int
name) { return find("name", name).firstResult(); } void persist(Entity entity) {} void delete(Entity entity) {} Entity findById(Id id) {} List<Entity> list(String query, Sort sort, Object... params) { return null; } Stream<Entity> stream(String query, Object... params) { return null; } long count() { return 0; } long count(String query, Object... params) { return 0; } } example: hibernate with panache

@holly_cummins #RedHat example: hibernate with panache @ApplicationScoped public class GreetingRepository
implements PanacheRepository<Greeting> { public Entity findByName(int name) { return find("name", name).firstResult(); } }

@holly_cummins #RedHat DAO example: hibernate with panache @ApplicationScoped public class
GreetingRepository implements PanacheRepository<Greeting> { public Entity findByName(int name) { return find("name", name).firstResult(); } } repository pattern

@holly_cummins #RedHat example: hibernate with panache

@holly_cummins #RedHat example: hibernate with panache active record pattern @Entity
public class Greeting extends PanacheEntity { public String name; public LocalDate issued; @Version public int version; public static List<Greeting> getTodaysGreetings() { return list("date", LocalDate.now()); } }

@holly_cummins why was this even hard? public class PanacheEntity {
public static <Entity extends PanacheEntity> List<Entity> listAll() { // but… how do we know which entity to query? throw new UnobtainiumException(); } }

public static <Entity extends PanacheEntity> List<Entity> listAll() { // but… how do we know which entity to query? throw new UnobtainiumException(); } } signature can be generic

public static <Entity extends PanacheEntity> List<Entity> listAll() { // but… how do we know which entity to query? throw new UnobtainiumException(); } } implementation cannot be generic signature can be generic

@holly_cummins here’s what we do @Entity public class Order extends
PanacheEntity { // … original class // injected in the bytecode // we add a Order.listAll method public static List<Order> listAll() { return DbOperations.listAll(Order.class); } }

@holly_cummins machine efficiency unlocked human efficiency we broke the tradeoff

@holly_cummins #RedHat but magic

@holly_cummins #RedHat magic should always be optional

@holly_cummins #RedHat doing less is efficient fighting bad magic is
not efficient

@holly_cummins optimise for real use, not demo-ware real efficiency

@holly_cummins what is the common factor behind our performance improvements?

@holly_cummins developer-zero on Quarkus redesigned Hibernate to “boot in advance”
what is the common factor behind our performance improvements?

@holly_cummins hyper-focussed performance engineer delivers big fixes to many open
source Java projects what is the common factor behind our performance improvements?

working on neighbouring projects big improvement to efficiency of Jackson with virtual threads

@holly_cummins #RedHat A lot of clever people made Quarkus so
efficient. Only some of them were Italian.

@holly_cummins #RedHat Emiliia Nesterovych Emmanuel Bernard Emre Kaplan Enrique gonzález
Martínez Enrique Mingorance Cano Eoin Gallinagh Eric Deandrea Eric Wittmann Erik Åsén Erik Mattheis Erin Schnabel Eugene Berman Evan Shortiss Fabricio Gregorio faculbsz Falko Modler Fedor Dudinskiy Felipe Carvalho dos Anjos Formentin Felipe Henrique Gross Windmoller Fernando Comunello Fernando Henrique fhavel Fikru Mengesha Filippe Spolti Florian Beutel Florian Bütler Florian Heubeck Florin Botis Foivos Zakkak Foobartender Fouad Almalki Francesco Nigro Francisco Javier Tirado Sarti Francois Steyn Frank Eichfelder franz1981 freakse-sa Fred Bricon Frédérc Blanc Freeman Fang Fu Cheng Gabriele Cardosi Galder Zamarreño galiacheng Gavin King Gavin Ray Geert Schuring Geoffrey De Smet Geoffrey GREBERT Georg Leber George Gastaldi manofthepeace Manyanda Chitimbo Marat Gubaidullin Marc Nuri Marc Schlegel Marc Wrobel Marcel Hanser Marcel Lohmann Marcell Cruz Marcelo Pereira Marcin Czeczko Marcin Kłopotek Marco Bungart Marco Schaub Marco Yeung Marco Zanghì Marcus Paulo Marek goldmann Marek Skacelik Marián Macik Mario Fusco MarioHNogueira Mark Lambert Mark Little Mark McLaughlin Mark Sailes marko-bekhta Markus Heberling Markus Himmel Markus Schwer Martin C. Richards Martin Grammelspacher Martin Kouba Martin Muzikar Martin Panzer Martin Weiler martin-kofoed-jyskebank-dk MartinWitt Marvin B. Lillehaug masini Matej Novotny Matej Vasek Matheus Cruz Mathias Holzer Matteo Mortari Matthias Andreas Benkard Matthias Cullmann mauroal Max Andersen Max Gabrielsson Max Rydahl Andersen Victor Hugo de Oliveira Molinar Vincent Sevel Vincent van Dam Vinícius Ferraz Campos Florentino Viswa Teja Nariboina Vladimir Konkov Vojtech Juranek Vratislav Hais w.glanzer Walter Medvedeo Wayne Ellis Werner Glanzer Willem Jan Glerum William Antônio Siqueira Wim goeman Wippermueller, Frank wojciech.stryjewski Xavier Xieshen xstefank Y. Luis Yann-Thomas LE MOIGNE Yannick Reifschneider YassinHajaj Yelzhas Suleimenov yesunch9 Yoann Rodière Yoshikazu Nojima Youngmin Koo Yubao Liu yugoccp Yukihiro Okada Zaheed Beita zanmagerl zedbeit Zheng Feng Žiga Deisinger Zineb Bendhiba zohar Zoran Regvart Шумов Игорь Юрьевич 出门三不惹 A lot of clever people made Quarkus so efficient. Only some of them were Italian.

@holly_cummins Ok, you don’t have to be Italian. But you
do have to graft.

@holly_cummins

@holly_cummins profile shave

@holly_cummins profile shave shave profile

@holly_cummins profile shave shave profile shave profile

@holly_cummins profile shave shave profile shave profile shave profile

@holly_cummins profile shave shave profile shave profile shave profile shave
profile

@holly_cummins profile shave shave profile shave profile shave profile shave
profile shave profile

@holly_cummins this is not easy stuff Franz the problem

@holly_cummins “OAAS: obsession as a service” - Francesco Nigro

small number of cores Netty http handling example: type pollution

lots of cores Netty http handling example: type pollution

what’s going on here? lots of cores example: type pollution

@holly_cummins to find out, Francesco Nigro and Andrew Haley read
20,000 lines of ASM ASM

@holly_cummins if (a instanceof Thing) problematic pattern:

@holly_cummins if (a instanceof Thing) problematic pattern: !!

@holly_cummins if (a instanceof Thing) problematic pattern: affects : !!

@holly_cummins if (a instanceof Thing) – Quarkus core – Netty
– Hibernate ORM – Hibernate Reactive – Vert.x – Smallrye Mutiny – Smallrye Common – Vert.x Web – Infinispan – Camel – Drools – Optaplanner – Java Class Library problematic pattern: affects : !!

@holly_cummins avoiding the problematic pattern sped Quarkus up a lot
(in many-core case)

@holly_cummins #RedHat private static int extractSize(Object it) { if (it
instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } else if (it.getClass().isArray()) { return Array.getLength(it); } else if (it instanceof Integer) { return ((Integer) it); } return 10; } slow on many-core systems

instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } else if (it.getClass().isArray()) { return Array.getLength(it); } else if (it instanceof Integer) { return ((Integer) it); } return 10; } // Note that we intentionally use "instanceof" to test interfaces as the last resort in order to mitigate the "type pollution” // See https://github.com/RedHatPerf/type-pollution-agent for more information if (it instanceof AbstractCollection) { return ((AbstractCollection<?>) it).size(); } else if (it instanceof AbstractMap) { return ((AbstractMap<?, ?>) it).size(); } else if (it instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } return 10; } slow on many-core systems 30% more throughput

instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } else if (it.getClass().isArray()) { return Array.getLength(it); } else if (it instanceof Integer) { return ((Integer) it); } return 10; } // Note that we intentionally use "instanceof" to test interfaces as the last resort in order to mitigate the "type pollution” // See https://github.com/RedHatPerf/type-pollution-agent for more information if (it instanceof AbstractCollection) { return ((AbstractCollection<?>) it).size(); } else if (it instanceof AbstractMap) { return ((AbstractMap<?, ?>) it).size(); } else if (it instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } return 10; } but …

instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } else if (it.getClass().isArray()) { return Array.getLength(it); } else if (it instanceof Integer) { return ((Integer) it); } return 10; } // Note that we intentionally use "instanceof" to test interfaces as the last resort in order to mitigate the "type pollution” // See https://github.com/RedHatPerf/type-pollution-agent for more information if (it instanceof AbstractCollection) { return ((AbstractCollection<?>) it).size(); } else if (it instanceof AbstractMap) { return ((AbstractMap<?, ?>) it).size(); } else if (it instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } return 10; } not a fan of the fix but …

instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } else if (it.getClass().isArray()) { return Array.getLength(it); } else if (it instanceof Integer) { return ((Integer) it); } return 10; } // Note that we intentionally use "instanceof" to test interfaces as the last resort in order to mitigate the "type pollution” // See https://github.com/RedHatPerf/type-pollution-agent for more information if (it instanceof AbstractCollection) { return ((AbstractCollection<?>) it).size(); } else if (it instanceof AbstractMap) { return ((AbstractMap<?, ?>) it).size(); } else if (it instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } return 10; } not a fan of the fix non-idiomatic but …

instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } else if (it.getClass().isArray()) { return Array.getLength(it); } else if (it instanceof Integer) { return ((Integer) it); } return 10; } // Note that we intentionally use "instanceof" to test interfaces as the last resort in order to mitigate the "type pollution” // See https://github.com/RedHatPerf/type-pollution-agent for more information if (it instanceof AbstractCollection) { return ((AbstractCollection<?>) it).size(); } else if (it instanceof AbstractMap) { return ((AbstractMap<?, ?>) it).size(); } else if (it instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } return 10; } not a fan of the fix non-idiomatic difficult to maintain but …

instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } else if (it.getClass().isArray()) { return Array.getLength(it); } else if (it instanceof Integer) { return ((Integer) it); } return 10; } // Note that we intentionally use "instanceof" to test interfaces as the last resort in order to mitigate the "type pollution” // See https://github.com/RedHatPerf/type-pollution-agent for more information if (it instanceof AbstractCollection) { return ((AbstractCollection<?>) it).size(); } else if (it instanceof AbstractMap) { return ((AbstractMap<?, ?>) it).size(); } else if (it instanceof Collection) { return ((Collection<?>) it).size(); } else if (it instanceof Map) { return ((Map<?, ?>) it).size(); } return 10; } not a fan of the fix non-idiomatic difficult to maintain machine efficiency my team’s efficiency but …

@holly_cummins #RedHat efficiency isn’t a one-time activity beware creeping performance
deterioration

@holly_cummins #RedHat a statistics story: how we missed regressions

@holly_cummins #RedHat a statistics story: how we missed regressions is
performance getting better or worse here?

@holly_cummins #RedHat a statistics story: how we missed regressions

@holly_cummins #RedHat a statistics story: how we missed regressions a
parametric change-detection algorithm meant this big regression masked other, smaller, regressions

@holly_cummins #RedHat a story: how we fixed regressions

@holly_cummins #RedHat a story: how we fixed regressions Roberto undid
two years of creep in one release

@holly_cummins #RedHat challenge assumptions

@holly_cummins #RedHat string comparison: who says you have to read
strings left-to-right? challenge assumptions

@holly_cummins #RedHat string comparison: who says you have to read
strings left-to-right? QUARKUS_REPEATED_PREFIX_FOO QUARKUS_REPEATED_PREFIX_BAR challenge assumptions

@holly_cummins ssssshhhhhhhh! it’s a secret! invest in your own Francesco
(being Italian is optional)

@holly_cummins one last trade-off

@holly_cummins sustainability saving planet doing stuff we want to do

@holly_cummins the vrroooom model gives hope but …

@holly_cummins

@holly_cummins naming is the hardest problem in computer science

@holly_cummins my vrroooom model

@holly_cummins #RedHat

@holly_cummins #RedHat these two columns are almost the same

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

@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

@holly_cummins #RedHat capacity Source: John O’Hara Setup: • REST +
CRUD • large heap • RAPL energy measurement Assumptions: climate impact at low load (single instance) lower is better

CRUD • large heap • RAPL energy measurement Assumptions: climate impact at low load (single instance) line length shows max throughput lower is better

CRUD • large heap • RAPL energy measurement Assumptions: climate impact at low load (single instance) Quarkus on JVM has the lowest carbon … because it has the highest throughput line length shows max throughput lower is better

@holly_cummins #RedHat saving planet coding how we wanna code we
beat the tradeoff

@holly_cummins machine efficiency helps us gain human efficiency

@holly_cummins efficient languages (too long; didn’t pay attention) tl;dpa

@holly_cummins efficient languages machine efficiency human efficiency (too long; didn’t
pay attention) tl;dpa

pay attention) tl;dpa challenge assumptions

pay attention) tl;dpa challenge assumptions only do work once

pay attention) tl;dpa challenge assumptions only do work once move work to where it hurts least

pay attention) tl;dpa challenge assumptions only do work once move work to where it hurts least index, index, index

pay attention) tl;dpa challenge assumptions only do work once move work to where it hurts least index, index, index efficiency needs continued investment

pay attention) tl;dpa challenge assumptions challenge assumptions only do work once move work to where it hurts least index, index, index efficiency needs continued investment

pay attention) tl;dpa challenge assumptions challenge assumptions tighten feedback loops only do work once move work to where it hurts least index, index, index efficiency needs continued investment

pay attention) tl;dpa challenge assumptions challenge assumptions tighten feedback loops only do work once move work to where it hurts least index, index, index efficiency needs continued investment don’t make humans tell the computer what the computer already knows

Zero Waste, Radical Magic, and Italian Graft – ...

Zero Waste, Radical Magic, and Italian Graft – Quarkus Efficiency Secrets

More Decks by Holly Cummins

Other Decks in Programming

Featured

Transcript