Project

General

Profile

Bug #2204

mismanagement of npme variable

Added by Mark Abraham over 2 years ago. Updated almost 2 years ago.

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

Description

mdrun -npme -1 -nb gpu leads to setting npme = 0 in runner() because GPUs are in use, and then DD setup code reports

Using 0 separate PME ranks, per user request

We can eliminate "per user request" in the short term, to stop reporting wrong things, but after that we should probably plan to separate the code that chooses npme (much of which is in domdec module) from the code that implements that choice, since this is going to be another complex aspect as we evolve more complex task assignment and hopefully better auto-tuning.

Associated revisions

Revision 66a29b6a (diff)
Added by Aleksei Iupinov almost 2 years ago

Remove potentially wrong "per user request" note from npme reporting

Refs #2204

Change-Id: Idd2127737b7b1af9cec9f7b547478b8b82cdb59a

History

#1 Updated by Mark Abraham about 2 years ago

  • Target version changed from 2016.4 to 2016.5

#2 Updated by Mark Abraham almost 2 years ago

  • Target version changed from 2016.5 to 2018
  • Affected version - extra info set to 2016.4
  • Affected version changed from 2016.4 to 2018-beta2

Not sure what is potentially good to fix here, but if we do we should probably not bother with release-2016

#3 Updated by Gerrit Code Review Bot almost 2 years ago

Gerrit received a related patchset '1' for Issue #2204.
Uploader: Aleksei Iupinov ()
Change-Id: gromacs~release-2018~Idd2127737b7b1af9cec9f7b547478b8b82cdb59a
Gerrit URL: https://gerrit.gromacs.org/7372

#4 Updated by Mark Abraham almost 2 years ago

  • Status changed from New to Resolved
  • Target version changed from 2018 to 2018-rc1

#5 Updated by Mark Abraham almost 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF