I have finished refactoring LmdbJava Benchmarks to use the latest third party database libraries, Java 25, automatic scaling of workloads to match available system memory, and execution on every commit (including both JMH benchmarking and report production with charts) via GitHub Actions.

We need to decide how we best want to manage benchmarks going forward, particularly given the importance of maintaining performance as part of #259.

The current state of the benchmark project enables us to run benchmarks on a timer basis or indeed on every commit to the main LmdbJava repository. But a proper benchmark requires a more stable environment than a GitHub Action can provide. Plus we don't currently have a mechanism for comparing branches, eg FFM compared with the present Unsafe-based buffers.

Comments and suggestions are invited.