SimVascular / SimVascular/svOneDSolver
Memory Usage
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 22
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
I've noticed that the 1D Solver requires a huge amount of memory (this is causing issues when running on the HPC clusters). I'm seeing around 25GB required for a 6 cycle simulation of a coronary model with coronary BCs. I think it's because the results are held in memory and not written to file until the simulation finishes. Might be use looking into how to reduce this, would really help with running parallel simulations.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported 25GB usage with a 6-cycle coronary model using coronary boundary conditions, ideally on an HPC cluster. Trace when simulation results are retained and written to file, then identify a way to reduce peak memory without changing results. Done means the same simulation uses materially less memory and still completes correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- hpc, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100