Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define an archiving mechanism and baselining #67

Open
1 task
FlorianDeconinck opened this issue May 22, 2024 · 0 comments
Open
1 task

Define an archiving mechanism and baselining #67

FlorianDeconinck opened this issue May 22, 2024 · 0 comments

Comments

@FlorianDeconinck
Copy link
Collaborator

FlorianDeconinck commented May 22, 2024

Previous benchmark have been hand made and stored - leading to some forgetfulness.

We need to be able to store them properly and draft a website/report that is very detailed and serve as base of truth. Nebulae wiki is one version controlled storage, for example.

We should also archive the results as long as they are compressed to a manageable size (.json of dycore timings, log of GEOS, data in general)

Parent: #65


  • Document workflow (and do required setup) for benchmark data/result save
@FlorianDeconinck FlorianDeconinck changed the title Define an archiving mechanism and baselining [GEOS] Define an archiving mechanism and baselining May 22, 2024
@FlorianDeconinck FlorianDeconinck changed the title [GEOS] Define an archiving mechanism and baselining Define an archiving mechanism and baselining Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant