Documentation on how to get max node performance with GraalVM

[OlegJakushkin]

Description

As a PoA chain hoster, I want to understand how to increase performance using GraaLVM to get better TPS.

Acceptance Criteria

• There is a doc outlining how to run GraalVM-based besu nodes to achieve top performance
  • Possible compilation arguments/parameters
  • Possible runtime parameters and what they depend on

Logs (if a change in behaviour)

• Currently, I see such performance differences on the same node types, distributed across 3 clusters when running [Simple benchmark from Caliper] (https://github.com/hyperledger-caliper/caliper-benchmarks/tree/main/benchmarks/scenario/simple) across 2 runs with 3 validators each in physically different location:
  
• This is the container image I currently use to build and run the GraalVM besu codebase:

FROM ghcr.io/graalvm/graalvm-community:21
RUN microdnf -y install findutils 
	
COPY . /besu

WORKDIR /besu
RUN ./gradlew nativeCompile --parallel  --dependency-verification=off
RUN ./gradlew installDist  --continue --parallel   --dependency-verification=off

EXPOSE 8545 8546 8547

CMD ["/besu/build/install/besu/bin/besu", "--help"]
ENTRYPOINT ["/besu/build/install/besu/bin/besu"]

Versions (Add all that apply)

• I tried on 24.10.0 codebase

[macfarla]

@ahamlat think you looked at GraalVM recently - there were some issues with mainnet (no fallbacks for native/JNI libs) but will it work for PoA? Any insights on this?