Project

General

Profile

Task #2435

identify and note about/tune task offload in GPU-bound runs

Added by Szilárd Páll over 1 year ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
mdrun
Target version:
-
Difficulty:
hard
Close

Description

There is a range of hardware/input combinations where the default eager offload of both NB and PME tasks is not beneficial. The limited scope testing that was also generally biased by our mostly high-end hardware did not bring out enough use cases to warrant better identifying severely GPU-limited cases and at least noting this or possibly auto-tuning it.

I suggest that we:
- create some heuristics and at least note in the log that the user should consider mixed / CPU PME if the run is very GPU bound
- look into auto-tuning PME task placement

Example use-case: https://www.mail-archive.com/gromacs.org_gmx-users@maillist.sys.kth.se/msg31467.html

History

#1 Updated by Szilárd Páll over 1 year ago

  • Description updated (diff)

#2 Updated by Mark Abraham over 1 year ago

Sounds great!

It feels like there should be a parent task for e.g. better auto-tuning.

Also available in: Atom PDF