PMIx Tools and Dynamic Workflows WG - Meeting of 2024 to adjust our schedule

[Isaías Alberto Comprés Ureña]

Hello everyone,

We plan to hold our first meeting of 2024 today at 17:00 German time.  The goal for today is to identify a time slot that will work for us.  We expect to resume regular WG activities in February.  

If you have a schedule conflict and cannot attend today, or at last year schedule (first Wednesday of the month at 17:00 German time) and would like to attend, please let us know and we can set up a doodle poll.

[Dominik Huber]

Hi Isaias,

I have a conflict today due to the HiPEAC Conference in Munich. This might also impact some other participants. Other than that the time slot usually works well for me.

Best regards,

Dominik

---

Von: pmix-foru...@googlegroups.com <pmix-foru...@googlegroups.com> im Auftrag von Isaías Alberto Comprés Ureña <com...@gmail.com>
Gesendet: Mittwoch, 17. Januar 2024 16:12:55
An: PMIx Standard Tools Working Group
Betreff: [pmix-forum-wg-tools] PMIx Tools and Dynamic Workflows WG - Meeting of 2024 to adjust our schedule

 

Hello everyone,

We plan to hold our first meeting of 2024 today at 17:00 German time.  The goal for today is to identify a time slot that will work for us.  We expect to resume regular WG activities in February.  

If you have a schedule conflict and cannot attend today, or at last year schedule (first Wednesday of the month at 17:00 German time) and would like to attend, please let us know and we can set up a doodle poll.

--
You received this message because you are subscribed to the Google Groups "PMIx Standard Tools Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pmix-forum-wg-t...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pmix-forum-wg-tools/92b4aead-74f1-4f66-8ac5-8f569c9e0896n%40googlegroups.com.

[Isaías Alberto Comprés Ureña]

Hello everyone,

The time slot for the calls remains unmodified: first Wednesday of the month, at 17:00 German time.  Our next meeting is therefore Wednesday, February 7th.

Today we had a conversation about preemption, and how it is relevant to dynamic workflows:

- Compute centers may define preemption policies, and PMIx needs to support them when defined.

- Can be combined with checkpointing, to ensure a preempted job preservers its progress .

    - Time allowed for checkpoint may be defined by the system, or negotiated with the job

- We need to define how the job is notified, e.g. event from pmix or signal, etc.

    - How can the application respond? An event back?

- Which attributes are there? Do we need new ones?

- Consider use cases, such as urgent computing, "power corridor"/band and/or billing situations (e.g. SuperMUC), etc.

    - Some research has been done on the scheduling front.

    - Power controls can introduce load imbalances and this can bring side effects, such as overloading message queues and/or memory.

        - Homogeneous performance at different power per unit, or

        - Same power per unit, but heterogeneous performance.

- Can benefit mixed-model workloads: e.g. MPI+X where X tends to be dynamic such as map-reduce or AI 

    - Use resources for epochs instead of holding them for the entirety of the excecution

    - Interest to ensure higher utilization by compute centers.

We will make a small survey about preemption in supercomputing and related fields (Isaias volunteers to start it).

Participants:

Ralph Castain

Norbert Eicker

Isaias Compres