[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[ptp-dev] Major breaking API change
|
Hi everyone,
I'm planning to commit a large number of changes to the PTP core
plugins at 5pm EDT on Monday. The purpose of these changes are to
improve the scalability of the model and the UI, particularly on
systems with large numbers of nodes, or when launching large jobs.
The changes are as follows:
1. Each model element can generate two types of event: child events
and element events. Child events are generated when any child of the
element is added/removed/changed. Element events are generated when
attributes on the element change. In the new scheme, only a single
child event may be generated, even if many child elements are
affected. This allows the resource manager implementation to reduce
the number of events that are sent, and allows the UI to optimize how
it displays the changes.
2. Rename/reduce the number of model events. There was considerable
overlap in the events that were generated by the model, so these have
now been consolidated. I've also renamed the events and event
listeners to better reflect their purpose.
These changes will mainly affect clients of the model (e.g. the
debugger). However, resource manager implementations will need to
update to the new interfaces. This was relatively painless for ORTE,
MPICH2, etc. so I don't expect any major problems with other RM
implementations.
If anyone has questions or comments, please let me know.
Greg