Repository navigation
Conversation
VEZY
changed the title
Contributor
Benchmark Results (Julia v1.12.1)Time benchmarks
Memory benchmarks
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The XPalm benchmark runs the current 0.7 model but compares its final LAI to a historical 0.6.1 value. Load the existing
v0.7.0-devoracle after checking its scenario metadata, weather hash, dates and full 4,160-day horizon. Historical release baselines, scientific fixtures and tolerances remain unchanged.Repeated full-output measurements also overlap large histories. Extract the first run's final state and runtime counters outside the timed operation, then release its history before the next sample. Non-inlined sample helpers keep later results and factory-owned model state collectible. Default callers still receive the first result unchanged. Lifetime tests cover both paths, sample counts and statistics.
The workflow still defaults to the complete matrix with three samples and every output mode. An optional diagnostic selects the existing full-length warmed no-output gate. Progress/resource logging and a bounded test step preserve evidence and artifact-upload time.
Validation:
034442e313f9b3878d67b216bf98a5e39c7dd3f3, PlantBiophysics12b0c1976a0177985437056c5fb01415c3e53e2e, released PlantGeomd5b005fa931a235bd1d55fcbe830e2e20321df26. Manifest and measurements are uploaded with the run.git diff --checkpass. Engine source and historical release baselines remain byte-identical to v0.15.0.The ordinary XPalm integration check still selects XPalm
main, whose PlantGeom compatibility stops at 0.19. It therefore fails during dependency resolution with PlantGeom 0.20, before tests. The compatible XPalm update is independently validated in XPalm PR134 and remains unmerged under the downstream release hold. This PR leaves the existing development integration workflow unchanged; its complete benchmark run above uses the explicit compatible candidate. The passing normal engine CI and explicit-candidate benchmark above are separate from this downstream-main resolver failure.