Limit 20 : Aggregate Collective Time
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c
- Domain
- performance
Research direction
Start by locating the code that produces the “Aggregate Collective Time” report and enforces the “top twenty” limit. Determine whether runtime configuration can control that limit or whether the report needs a code change; done means the report exposes all collective-operation entries as requested.
Written by the indexing model from the issue text.
Description
I would like to get information of all the collective operation rather top 20 shown in "Aggregate Collective Time" table. Is it possible to define any such env variable at runtime or change in the code to enable this information?
eg.
---------------------------------------------------------------------------
@--- Aggregate Collective Time (top twenty, descending) -------------------
---------------------------------------------------------------------------
Call MPI Time % Comm Size Data Size
Allreduce 4.08 256 - 511 8 - 15
Allreduce 2.31 256 - 511 0 - 7
Barrier 0.0468 256 - 511 0 - 7
Bcast 0.0343 256 - 511 512 - 1023
- Dominant language
- C
- Stars
- 112
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from llnl/mpiP
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
-
MPI 4.0 SupportOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Communication matrixOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
ARM supportOpen
Difficulty 4/5 3-5 days Newbie friendliness 30/100
Similar issues
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
netdata/netdata#24062 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
riscv-software-src/riscv-isa-sim#2448 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
NabuCasa/silabs-firmware-builder#231 · 1 comment ·