Details
-
Enhancement
-
Resolution: Done
-
Major
-
None
-
None
Description
In UNICAST3 we have 1 send- and 1 receive-table for every member, e.g. if we have A, B and C, and A sent unicast messages to all members and received unicasts from all members, then A has send and receive tables for A, B and C.
An optimization is to merge A's send and receive table for itself (A):
- A sends a message to itself and adds it to the send-table for A
- A receives a message from itself and adds it to the send-table for A as well (not the receive-table !)
- A removes as many messages from the send-table for A as possible and delivers them
The resulting optimizations are:
- 1 less table for every member
- When a message from self has been received, we don't need to send an ACK because the receive-table is the send-table and therefore low/hd/hr have already been adjusted (less traffic)