Qute - try to avoid type/cache pollution in the EvaluatorImpl

[mkouba]

[geoand]

@mkouba just for the interest of completeness, it would be nice to link to the benchmark you used and the specs of the machine it was run on in the description.

[mkouba]

@mkouba just for the interest of completeness, it would be nice to link to the benchmark you used and the specs of the machine it was run on in the description.

For sure. I always use https://github.com/mkouba/qute-benchmarks/ to test qute and forgot to add the link here ;-).

And the machine was a dedicated box with Ubuntu Server 20.04.4 LTS, Linux 5.4.0-125-generic, openjdk 11.0.11, Intel i5-6260U with 4 cores and 16GB RAM.

[geoand]

4 cores

If the benchmark is run on a machine with more cores, there should be an even bigger speedup :)

[quarkus-bot]

Failing Jobs - Building 3573ab9

Status	Name	Step	Failures	Logs	Raw logs
⌛	JVM Tests - JDK 11	Build	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 17
✖	JVM Tests - JDK 17 MacOS M1	Set up runner	⚠️ Check →	Logs	Raw logs
✖	JVM Tests - JDK 18	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 18 #

- Failing: integration-tests/logging-gelf 

📦 integration-tests/logging-gelf

✖ io.quarkus.logging.gelf.it.GelfLogHandlerTest.test line 32 - More details - Source on GitHub

org.awaitility.core.ConditionTimeoutException: Assertion condition defined as a io.quarkus.logging.gelf.it.GelfLogHandlerTest expected: not <null> within 20 seconds.
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:167)
	at org.awaitility.core.AssertionCondition.await(AssertionCondition.java:119)