Abnormal time consumption on "geosx::SiloOutput::Execute" for some HF simulations
@rrsettgast is already working on this.
Since Oct 12, 2020.
- Dominant language
- C++
- Stars
- 287
- Forks
- 109
- Avg merge
- 4d 41m
- Merged PRs (30d)
- 5
Description
Describe the bug
I am running some hydraulic fracturing simulations with the most recent GEOSX, and found that for some (not all) HF examples, a large portion of time was consumed on "geosx: SiloOutput::Execute". For example, for a simple PKN example with 10 by 10 by 10 mesh, the total running time was 414.9 s on a single core while 403.5 s was spent on "geosx: SiloOutput::Execute". Following are time report for this example. I also attached the input file for this PKN example.
To Reproduce
Run the attached input "PKN_Isotropic.xml" with caliper output
Expected behavior
Abnormal time consumption on "geosx: SiloOutput::Execute".
Platform (please complete the following information):
- Machine: LLNL/Quartz
- Compiler: clang 10.0.0
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.
Assessment
This issue has not been assessed yet.