Re: Question: "Garbage-Free" AbstractFilter#filter(...) methods.

We definitely make use of the non-vararg methods all over our code. While it's true that garbage collector technology has improved to keep pause times small and consistent with heap growth, that still doesn't mean that the benefits of low garbage code should be ignored. We see it as a two pronge

Re: Question: "Garbage-Free" AbstractFilter#filter(...) methods.

Hi Remko, On 2.03.2025 04:27, Remko Popma wrote: In my work we create trading applications that send orders to the stock exchange when market conditions change. If the JVM would decide to stop the world to collect garbage, we might not get the orders sent out in time. Our whole stack (messagi

Re: Question: "Garbage-Free" AbstractFilter#filter(...) methods.

Garbage free is mostly about predictable latency. In my work we create trading applications that send orders to the stock exchange when market conditions change. If the JVM would decide to stop the world to collect garbage, we might not get the orders sent out in time. Our whole stack (messag

Question: "Garbage-Free" AbstractFilter#filter(...) methods.

Hello Dev Team, I am a totally fresh "committer" so forgive me if I ask a silly question. I got into a discussion with Piotr about the Log4j Filters and the overloaded filter methods (14 in total) and asked if the extra API is necessary when there is a varargs "filter(, final Object ... par