Skip to content

Conversation

@JavierCladellas
Copy link
Collaborator

@JavierCladellas JavierCladellas commented Oct 30, 2024

Main changes:

  • Created the benchmark.yml workflow that launches the tests on a given machine (via configs on girder), and creates a PR (containing only docs) with the new benchmark reports.
  • Added some scripts used by the ci under src/feelpp/scripts/

⚠️ NOTE ⚠️
It has only been tested on gaya, with a builtin config and apptainer config. Apptainer config seems to have a bug concerning MPI bindings, but this bug should be independent of the pipeline.

@JavierCladellas
Copy link
Collaborator Author

Merge #94 before.

@JavierCladellas JavierCladellas marked this pull request as ready for review November 8, 2024 08:29
@JavierCladellas JavierCladellas added the github_actions Pull requests that update GitHub Actions code label Nov 8, 2024
@JavierCladellas JavierCladellas changed the title 103 create workflow for running benchmarks resolves: 103 create workflow for running benchmarks Nov 8, 2024
@JavierCladellas
Copy link
Collaborator Author

@prudhomm @vincentchabannes Benchmarks can now be triggered (after workflow is in master) via repository and workflow dispatch by providing the machines and benchmark json configs via a girder ID.

Apptainer is not ready yet: bug related with mpi

Parameters are:

Copy link
Member

@prudhomm prudhomm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some hard coded paths, we need at some point in the future to change this

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think that will work on eurohpc systems

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you didn't use the work in feelpp-kub it seems

Comment on lines +7 to +8
"reframe_base_dir":"/data/home/cladellash/benchmarking/build/reframe",
"reports_base_dir":"/data/home/cladellash/benchmarking/reports/"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the path should not be a personal one

"output_directory": "/data/scratch/cladellash/feelppdb/toolboxes/heatlfuid/eye",
"use_case_name": "eye",
"options": [
"--config-files /data/scratch/cladellash/feelppdb/input_data/eye/eye-{{parameters.position.value}}.cfg /data/scratch/cladellash/feelppdb/input_data/eye/pc_{{parameters.solver.value}}.cfg",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hardcoded path ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it should not be a personal path and probably relative to some root path for the framework

"--heat-fluid.heat.scalability-save=1",
"--heat-fluid.fluid.scalability-save=1",
"--repository.append.np 0",
"--heat-fluid.json.patch='{\"op\": \"replace\",\"path\": \"/Meshes/heatfluid/Import/filename\",\"value\": \"/data/home/saigre/pulications/mesh.eye/mesh/Mr/{{parameters.meshes.value}}/Eye_Mesh3D_p{{parameters.nb_tasks.tasks.value}}.json\" }'"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

pulications ? @thomas-saigre ?

@prudhomm
Copy link
Member

@JavierCladellas isn't it possible to split the json describing the benchmark and avoid duplicating eg the plot section between apptainer and builting ?

@JavierCladellas
Copy link
Collaborator Author

@JavierCladellas isn't it possible to split the json describing the benchmark and avoid duplicating eg the plot section between apptainer and builting ?

This is already done in #109 . The benchmark configuration should now be modified as little as possible. Also, plots section will be moved to a separate file in #111

@prudhomm prudhomm merged commit 4b38446 into master Nov 13, 2024
3 checks passed
@prudhomm prudhomm deleted the 103-create-workflow-for-running-benchmarks branch November 13, 2024 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement A new feature or request github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

create workflow for running benchmarks

3 participants