Skip to content

Conversation

@JavierCladellas
Copy link
Collaborator

Added memory to job option. It can now be specified under the memory field in the benchmark configuration.
Functional at the moment, but not optimal nor scalable.
Implementation is not enough general. I'm afraid it won't work for a scheduler other that slurm.

This should be generalized... Not scalable atm
@JavierCladellas JavierCladellas added enhancement A new feature or request benchmarking Issues related to benchmarking labels Dec 17, 2024
@JavierCladellas JavierCladellas self-assigned this Dec 17, 2024
@JavierCladellas JavierCladellas linked an issue Dec 17, 2024 that may be closed by this pull request
@netlify
Copy link

netlify bot commented Dec 17, 2024

Deploy Preview for benchmarking-polite-crostata-92f389 ready!

Name Link
🔨 Latest commit a50f1c4
🔍 Latest deploy log https://app.netlify.com/sites/benchmarking-polite-crostata-92f389/deploys/6761a725a9a5120008122dfb
😎 Deploy Preview https://deploy-preview-201--benchmarking-polite-crostata-92f389.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@JavierCladellas JavierCladellas merged commit ea49f8e into master Dec 20, 2024
10 checks passed
@JavierCladellas JavierCladellas deleted the 176-specify-memory branch December 20, 2024 08:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

benchmarking Issues related to benchmarking enhancement A new feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Specify memory

4 participants