Project

General

Profile

Bug #1158

PME time in log file incorrect with -ntomp_pme > -ntomp

Added by Berk Hess almost 5 years ago. Updated almost 5 years ago.

Status:
Closed
Priority:
Low
Assignee:
Category:
mdrun
Target version:
-
Affected version - extra info:
4.6
Affected version:
Difficulty:
uncategorized
Close

Description

The time in the log file spent in PME, but not the cycles, is always calculated based on the PP thread count, not the PME thread count.

pme_timing_test.tbz2 (6.85 MB) pme_timing_test.tbz2 Mikhail Plotnikov, 03/04/2013 12:15 PM

Associated revisions

Revision 4f8926df (diff)
Added by Berk Hess almost 5 years ago

fixed PME time print with -ntomp_pme != -ntomp

Fixes #1158

Change-Id: I9028e6309b8802125e91935e87d96b341ec30f77

Revision 21409207 (diff)
Added by Berk Hess over 4 years ago

fixed PME time print with -ntomp_pme != -ntomp

Fixes #1158

Change-Id: I9028e6309b8802125e91935e87d96b341ec30f77

History

#1 Updated by Mikhail Plotnikov almost 5 years ago

PME timing and reported number of PME threads is still incorrect in case -ntomp_pme is not set, but number of PME threads is taken from OMP_NUM_THREADS variable. Please use attached reproducer for the problem. It uses 2 nodes, one with 8 PP ranks and OMP_NUM_THREADS=2 and another with 4 PME ranks and OMP_NUM_THREADS=4. It has small README with steps to reproduce.

#2 Updated by Roland Schulz almost 5 years ago

  • Status changed from New to Closed

Mikhail could you please open a separate bug for the issue you found? It is related but not the same as this one. This one is submitted and fixed.

Also available in: Atom PDF