Merge pull request #27 from ludovic111/repeated-core-client
Record three matched-view client pairs and Mac first-test guide
This commit is contained in:
@@ -10,6 +10,8 @@ Download **horizon-mac-starter-0.20.0.zip** from [Releases](https://github.com/l
|
||||
|
||||
Use native **Java 25 ARM64**, maximum heap **6144 MiB**, minimum **512 MiB** on your 16 GB M2 Pro. Prism can download Java automatically. Start at 1280×800 or 1920×1200; full Retina resolution is a larger GPU workload. [START-HERE.txt](packs/START-HERE.txt) has details. The same `.mrpack` files import into Prism on Windows and Linux.
|
||||
|
||||
If Prism is already installed, follow the [Mac import and first comparison guide](docs/mac-first-test.md).
|
||||
|
||||
| Profile | Full-detail chunks | Distant LOD radius | Suggested maximum heap |
|
||||
| --- | ---: | ---: | ---: |
|
||||
| baseline | 12 | none | 6144 MiB |
|
||||
@@ -43,7 +45,8 @@ The latter adds only the pinned core performance mods and leaves every original
|
||||
controller disabled. Then test balanced separately for its additional distant
|
||||
terrain. Matching captured settings does not prove pixel-identical rendering.
|
||||
[Core comparison protocol and selected observations](docs/core-performance.md)
|
||||
include one software-rendered pair; M2 performance remains unmeasured.
|
||||
include three repeated matched-view software-rendered pairs with 14–21% higher
|
||||
FPS in this workload; M2 performance remains unmeasured.
|
||||
|
||||
The optional `queue-wait` pack yields during pending distant-terrain debounce retries; `adaptive-queue` combines it with the existing controllers. [Queue experiment and measurement limits](docs/debounce-queue.md).
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@@ -12,6 +12,68 @@ such as Transition and Trender in this observed core run. The comparator treats
|
||||
these software changes as explicit experiment variables. Matching configuration
|
||||
is not proof of pixel-identical rendering or exhaustive gameplay equivalence.
|
||||
|
||||
## Three repeated pairs on 0.20.0
|
||||
|
||||
The later series uses the exact published 0.20.0 mod with fresh JVMs and identical
|
||||
initial private world copies. Each run warms for 180 seconds in focused gameplay,
|
||||
then records frames and integrated-server ticks for 120 seconds. A separate test
|
||||
fixture in both profiles holds the same stationary camera. It is absent from
|
||||
playable packs. The workload remains 12 full-detail / 12 simulation chunks,
|
||||
1280×800, FOV 70, no LOD/shaders, G1, compact headers and a 3 GiB maximum heap.
|
||||
Private copies use Peaceful difficulty and a fixed noon clock/weather; distributed
|
||||
packs retain normal rules. All original experimental controllers are disabled.
|
||||
|
||||
| Pair | Baseline FPS | Core FPS | Baseline peak RSS | Core peak RSS | Baseline CPU | Core CPU |
|
||||
| --- | ---: | ---: | ---: | ---: | ---: | ---: |
|
||||
| 1 | 5.39 | 6.53 | 2,310.68 MiB | 2,043.46 MiB | 2.931 cores | 2.898 cores |
|
||||
| 2 | 5.55 | 6.32 | 2,572.06 MiB | 2,031.07 MiB | 2.928 cores | 2.981 cores |
|
||||
| 3 | 5.39 | 6.52 | 2,172.38 MiB | 2,121.73 MiB | 2.942 cores | 2.950 cores |
|
||||
|
||||
Paired average-FPS changes are **+21.28%, +14.00%, +20.96%**. Their arithmetic
|
||||
mean is +18.75%; this is a descriptive average of three changes, not a pooled
|
||||
frame estimate or a statistical significance claim. The slowest-1%-average rate
|
||||
is higher in all pairs, while p95 frame intervals are 8.43–21.25% lower. Peak
|
||||
sampled RSS changes are **−11.56%, −21.03%, −2.33%**. Memory varies substantially
|
||||
across fresh processes, so the earlier single pair's 22% reduction is not a
|
||||
stable memory-saving estimate.
|
||||
|
||||
Average process CPU changes are −1.11%, +1.81%, +0.30%: there is no consistent
|
||||
absolute CPU reduction while rendering more frames. Peak sampled JVM heap is
|
||||
slightly higher in the third core run. GC accounting time is 113→92 ms, 57→154 ms
|
||||
and 157→96 ms across the three pairs, so it is mixed too. These are collector
|
||||
MXBean totals, not JFR stop-the-world pause measurements; no JFR profiling runs
|
||||
alongside these captures.
|
||||
|
||||
Every accepted run has nonempty frame/tick CSVs with verified counts and mean
|
||||
durations, zero excluded frames or dropped samples, matching captured settings
|
||||
and no visual-setting changes. Sampled tick-manager state remains normal at
|
||||
20 configured TPS with no observed freeze, step, sprint or rate changes. Observed
|
||||
invocation throughput ranges from 19.997 to 20.006 TPS; mean tick execution time
|
||||
is 26.43–32.91% lower with core. This stationary integrated-server workload does
|
||||
not establish capacity for a populated dedicated server. Saved cameras, positions,
|
||||
clock/rules and clean process exits are checked for every run. All three real
|
||||
JSON/CSV pairs pass desktop/mobile comparison and chart checks.
|
||||
|
||||
The original third-pair candidate lost focus when the headless input tool's
|
||||
single long sleep overflowed and its keyboard disappeared. Its 448 eligible
|
||||
frames, 211 excluded frame starts and 1,391 measured ticks over about 120 seconds
|
||||
are excluded. The preceding valid baseline is retained separately as unpaired
|
||||
data. The complete third pair was repeated from fresh copies after replacing
|
||||
the long sleep with several shorter sleeps in one persistent process and adding
|
||||
an input-process liveness check. Neither excluded attempt enters the summary.
|
||||
|
||||
The [selected repeated observations](../benchmarks/core-client-repeats-2026-10-04/live-observations.json)
|
||||
include all six accepted runs, the excluded attempts, each pair's comparison,
|
||||
loaded mod identities and private capture/fixture hashes. This is still one
|
||||
stationary view on an i7-7500U Linux **llvmpipe software renderer**. Baseline is
|
||||
always first within each pair. OS cache, JIT, entity activity and thermal effects
|
||||
remain uncontrolled variables. Three pairs do not prove a universal improvement;
|
||||
Apple Silicon/native GPU performance, movement and terrain generation remain to
|
||||
be measured. See the [Mac first-test guide](mac-first-test.md) for a matched-view
|
||||
comparison on the user's hardware.
|
||||
|
||||
## Earlier single pair on 0.19.0
|
||||
|
||||
The selected 4 October 2026 live observations use separate private world copies,
|
||||
a stationary camera, native Linux x64 Java 25, G1, compact headers and the same
|
||||
3 GiB maximum heap. The test copies use Peaceful difficulty and a noon clock with
|
||||
@@ -39,7 +101,8 @@ These are descriptive observations, not a statistical or universal speedup claim
|
||||
They do not isolate which mod caused a difference. Entity activity, completion
|
||||
of rendering work, cache/JIT and thermal state remain possible variables. RSS
|
||||
excludes a complete GPU/unified-memory measurement; Apple Silicon performance
|
||||
remains unmeasured. Hardware graphics and repeated alternating trials are needed.
|
||||
remains unmeasured. Hardware graphics measurements remain needed; the separate repeated series above
|
||||
uses a different warm-up protocol and must not be pooled with this pair.
|
||||
|
||||
Preceding JFR counter rates for the server and render thread are lower with the
|
||||
core stack, but total and longest measured GC pauses are higher in that profile.
|
||||
|
||||
@@ -0,0 +1,88 @@
|
||||
# First test on the M2 Pro Mac
|
||||
|
||||
For the 16 GB M2 Pro, start with the published 0.20.0 packs. The client has been
|
||||
built on Apple Silicon macOS; gameplay and FPS on this Mac remain unmeasured.
|
||||
The Linux software-rendering observations do not predict an M2 speedup.
|
||||
|
||||
## Import after installing Prism
|
||||
|
||||
1. Download [horizon-mac-starter-0.20.0.zip](https://github.com/ludovic111/minecraft-optimization-lab/releases/download/v0.20.0/horizon-mac-starter-0.20.0.zip)
|
||||
and extract it in Finder.
|
||||
2. In Prism, choose **Add Instance > Import**, then select
|
||||
`horizon-m2-balanced-0.20.0.mrpack` from the extracted folder. The individual
|
||||
`.mrpack` is the import file; the starter ZIP contains several different packs.
|
||||
[Prism's import guide](https://prismlauncher.org/wiki/help-pages/zip-import/)
|
||||
describes the supported archive formats.
|
||||
3. Sign into your Microsoft account inside Prism, using your own Java Edition
|
||||
license. This project needs no account credentials.
|
||||
4. Open Prism's global **Settings > Java** and enable **Autodetect Java version**
|
||||
and **Auto-download Mojang Java**. This pack requires Java 25. On Apple Silicon,
|
||||
use ARM64/aarch64 Java. If you select Java manually, use the instance's
|
||||
**Edit > Settings > Java > Java installation > Auto-Detect** and select native
|
||||
Java 25. [Prism's Java guide](https://prismlauncher.org/wiki/getting-started/installing-java/)
|
||||
explains automatic downloads and manual selection.
|
||||
5. In the instance's **Edit > Settings > Java**, enable the Memory override and
|
||||
set maximum memory to **6144 MiB**, minimum to **512 MiB**. This is a starting
|
||||
heap budget, not a measurement of total process or unified GPU memory.
|
||||
6. Launch and create a new test world, or use a copy of a Minecraft 26.3 world.
|
||||
Save, quit, reopen and check normal movement, breaking/placing blocks and
|
||||
inventory interaction before benchmarking. Start at a modest window size,
|
||||
such as 1280×800; the recorder reports the actual framebuffer dimensions,
|
||||
which may differ from the logical window size on a Retina display.
|
||||
|
||||
Balanced uses 12 full-detail chunks and a 128-chunk distant terrain radius.
|
||||
Allow the distant cache to settle. Distant terrain uses simplified geometry and
|
||||
does not extend normal simulation. The cinematic and Vulkan packs are separate
|
||||
experiments to try after this first launch succeeds.
|
||||
|
||||
## Measure performance at the same view distance
|
||||
|
||||
Import `horizon-baseline-0.20.0.mrpack` and
|
||||
`horizon-core-performance-0.20.0.mrpack` from the same starter folder. Both use
|
||||
12 full-detail chunks, 12 simulation chunks and no distant LOD or shaders. Core
|
||||
adds the pinned performance mods; all original experimental controllers are off.
|
||||
Comparing these two isolates the core stack more closely than comparing baseline
|
||||
with balanced's additional distant terrain.
|
||||
|
||||
Use identical separate world copies, the same Java/heap/JVM flags, actual
|
||||
framebuffer size, FOV, graphics quality, VSync, FPS limit and camera route. Close
|
||||
other game instances, plug in the Mac and keep its power mode consistent. Use
|
||||
uncapped FPS with VSync off for both measurements if you want to measure available
|
||||
throughput; return to a display-appropriate cap or VSync for everyday play.
|
||||
|
||||
Warm each run for at least three minutes after entering the world and dismissing
|
||||
menus. Longer generation workloads may need more time. Press **F8** (possibly
|
||||
**Fn+F8**) in focused gameplay for a 120-second recording. Keep the view or route
|
||||
consistent and avoid menus during recording. After it finishes, save and quit.
|
||||
Repeat three pairs in this order:
|
||||
|
||||
| Pair | First run | Second run |
|
||||
| --- | --- | --- |
|
||||
| 1 | baseline | core-performance |
|
||||
| 2 | baseline | core-performance |
|
||||
| 3 | baseline | core-performance |
|
||||
|
||||
This alternates profiles but always puts baseline first within a pair. It reduces
|
||||
dependence on one run; it does not remove order, cache or thermal effects. Keep
|
||||
fresh terrain exploration separate from already-generated terrain. Also test
|
||||
normal gameplay after the stationary view; matching settings is not exhaustive
|
||||
gameplay or visual equivalence.
|
||||
|
||||
## Read the results
|
||||
|
||||
Open each instance's Minecraft folder in Prism and find `horizon-benchmarks/`.
|
||||
Keep each run's frame JSON/CSV and tick JSON/CSV together. Open
|
||||
`Compare-Benchmarks.html` from the starter folder and select one baseline frame
|
||||
JSON plus its CSV and the paired core frame JSON plus its CSV. Then compare the
|
||||
paired tick files separately. The viewer works locally without uploading files.
|
||||
|
||||
Check settings mismatches, exclusions, dropped samples and tick-state warnings
|
||||
before comparing FPS, p95/p99 frame intervals, peak sampled RSS and average process
|
||||
CPU. Compare all three pairs rather than selecting the best result. Normal tick
|
||||
invocation throughput should remain near 20 TPS; inverse tick execution duration
|
||||
is not TPS. RSS is sampled once per second and does not cover all unified GPU
|
||||
memory. See [tick-state limits](tick-state.md) and [memory limits](process-memory.md).
|
||||
|
||||
Finally test balanced for the longer horizon using the same route and resolution,
|
||||
with a settled distant cache. Treat its extra view distance as a changed visual
|
||||
workload, then decide whether the appearance and performance meet your goal.
|
||||
@@ -46,7 +46,7 @@ jfr summary .local/baseline.jfr
|
||||
jfr print --events jdk.ExecutionSample,jdk.GarbageCollection .local/baseline.jfr > .local/baseline-events.txt
|
||||
```
|
||||
|
||||
Collect CPU profiles, allocation/GC information, frame-time percentiles, server tick-time percentiles, and relevant GPU timings. JFR samples alone do not measure FPS or GPU cost. JVM compilation/warm-up, profiling overhead, world generation, and background activity must be controlled when comparing runs. No gameplay baseline has been collected by this repository's initial setup.
|
||||
Collect CPU profiles, allocation/GC information, frame-time percentiles, server tick-time percentiles, and relevant GPU timings. JFR samples alone do not measure FPS or GPU cost. JVM compilation/warm-up, profiling overhead, world generation, and background activity must be controlled when comparing runs. The [core comparison](core-performance.md) now contains stationary Linux software-rendering observations; Mac GPU, movement/generation and populated dedicated-server measurements remain open.
|
||||
|
||||
## First native integration experiment
|
||||
|
||||
|
||||
@@ -158,7 +158,12 @@ The local Linux host uses **Mesa llvmpipe software rendering**. It is useful for
|
||||
|
||||
CI compiles/builds on Linux, Windows and Apple Silicon macOS. Successful compilation is not graphics, authentication, UI or Mac-driver runtime validation. macOS 27 and the user's actual M2 Pro have not been tested here. Optional cinematic shaders and Vulkan are experiments; the OpenGL balanced pack is the first manual test.
|
||||
|
||||
No numerical game speedup, least-memory claim, exhaustive vanilla equivalence, universal GPU support, or 50-active-player result is claimed. Worlds need copies, repeated matched routes and real hardware measurements before decisions about deeper replacements. New terrain generation and steady-state rendering are separate workloads.
|
||||
The [core comparison](core-performance.md) records numerical observations for
|
||||
matched software-rendered workloads. They do not establish a Mac or hardware-GPU
|
||||
speedup, least-memory result, exhaustive vanilla equivalence, universal GPU
|
||||
support, or a 50-active-player result. Worlds need copies, repeated matched routes
|
||||
and real hardware measurements before decisions about deeper replacements. New
|
||||
terrain generation and steady-state rendering are separate workloads.
|
||||
|
||||
## Release content
|
||||
|
||||
|
||||
Reference in New Issue
Block a user