Progressive messages: tracking message progress through events
<p>This thesis introduces the Progressive Messages model of communication. It is an event-driven framework for building scalable parallel and distributed computing applications on modern networks. In particular, the paradigm provides notification of message termination. That is, when a message...
| Yazar: | |
|---|---|
| Diğer Yazarlar: | |
| Materyal Türü: | Tez |
| Dil: | English |
| Baskı/Yayın Bilgisi: |
2011
|
| _version_ | 1826315991850680320 |
|---|---|
| author | Aycock, CC |
| author2 | Brent, RP |
| author_facet | Brent, RP Aycock, CC |
| author_sort | Aycock, CC |
| collection | OXFORD |
| description | <p>This thesis introduces the Progressive Messages model of communication. It is an event-driven framework for building scalable parallel and distributed computing applications on modern networks. In particular, the paradigm provides notification of message termination. That is, when a message succeeds or fails, the user’s application can capture an event (often through a callback) and perform a designated action.</p> <p>The semantics of the Progressive Messages model are defined as an extension to the message-driven model, which is like an asynchronous RPC. Together, these models can be contrasted to the message-passing model (the basis of Sockets and MPI), which has no event notification.</p> <p>Using Progressive Messages allows for a more scalable design than permitted by either the message-passing or message-driven model. In particular, Progressive Messages can handle communication concurrently with computation, which means that one process does not need to wait in order to service a request or response from another process. This overlap leads to more efficiency.</p> <p>As part of the study of Progressive Messages, we create the MATE (Message Alerts Through Events) library, which is a prototype API that supports event notification in communication. This API was implemented in both MPI and InfiniBand <em>verbs</em> (OpenFabrics). "Unit tests" of network metrics shows that there is some latency in event-driven message handling, though it is difficult to determine if the source of the latency is hardware or software based.</p> <p>The goal of the Progressive Messages model is that parallel and distributed computing applications will be easier to build and will be more scalable.</p> |
| first_indexed | 2024-03-06T20:03:52Z |
| format | Thesis |
| id | oxford-uuid:28425a0e-cd08-4a0a-b978-74adc4901a58 |
| institution | University of Oxford |
| language | English |
| last_indexed | 2024-12-09T03:36:08Z |
| publishDate | 2011 |
| record_format | dspace |
| spelling | oxford-uuid:28425a0e-cd08-4a0a-b978-74adc4901a582024-12-01T19:43:03ZProgressive messages: tracking message progress through eventsThesishttp://purl.org/coar/resource_type/c_db06uuid:28425a0e-cd08-4a0a-b978-74adc4901a58EnglishOxford University Research Archive - Valet2011Aycock, CCBrent, RP<p>This thesis introduces the Progressive Messages model of communication. It is an event-driven framework for building scalable parallel and distributed computing applications on modern networks. In particular, the paradigm provides notification of message termination. That is, when a message succeeds or fails, the user’s application can capture an event (often through a callback) and perform a designated action.</p> <p>The semantics of the Progressive Messages model are defined as an extension to the message-driven model, which is like an asynchronous RPC. Together, these models can be contrasted to the message-passing model (the basis of Sockets and MPI), which has no event notification.</p> <p>Using Progressive Messages allows for a more scalable design than permitted by either the message-passing or message-driven model. In particular, Progressive Messages can handle communication concurrently with computation, which means that one process does not need to wait in order to service a request or response from another process. This overlap leads to more efficiency.</p> <p>As part of the study of Progressive Messages, we create the MATE (Message Alerts Through Events) library, which is a prototype API that supports event notification in communication. This API was implemented in both MPI and InfiniBand <em>verbs</em> (OpenFabrics). "Unit tests" of network metrics shows that there is some latency in event-driven message handling, though it is difficult to determine if the source of the latency is hardware or software based.</p> <p>The goal of the Progressive Messages model is that parallel and distributed computing applications will be easier to build and will be more scalable.</p> |
| spellingShingle | Aycock, CC Progressive messages: tracking message progress through events |
| title | Progressive messages: tracking message progress through events |
| title_full | Progressive messages: tracking message progress through events |
| title_fullStr | Progressive messages: tracking message progress through events |
| title_full_unstemmed | Progressive messages: tracking message progress through events |
| title_short | Progressive messages: tracking message progress through events |
| title_sort | progressive messages tracking message progress through events |
| work_keys_str_mv | AT aycockcc progressivemessagestrackingmessageprogressthroughevents |