Micrometer performance improvements

[brunobat]

Description

The current way we are using Micrometer has negative performance impacts, as described in this blog post from @tsegismont:
https://vertx.io/blog/micrometer-metrics-performance/

In a nutshell:

• fil­ter­ing tags up front in­stead of using a Mi­crom­e­ter MeterFilter
• avoid­ing re­dun­dant copies when com­bin­ing tags
• look­ing up me­ters once if their tags are known in ad­vance
• use a MeterProvider when some tags can be de­ter­mined only after an event oc­cured.

This issue will be the parent issue of many enhancements that should happen on the quarkus-micrometer extension, mainly in the io.quarkus.micrometer.runtime.binder package classes.

Will create an issue per package because this can be a good first issue for someone. To help with this, the Vert.x package PR will serve as a reference implementation.

List of child issues:

• Micrometer performance improvements - vert.x #40506
• Micrometer performance improvements - Stork and binder #40597 (PR available)
• Micrometer performance improvements - runtime package #40598
• Micrometer performance improvements - mpmetrics package #40599

You just need to pick one for you.

[quarkus-bot]

/cc @ebullient (micrometer)

[brunobat]

This is done

[tsegismont]

@brunobat great! Have you been able to measure improvements?

[brunobat]

Not yet. I' m still working on the performance setup.