P2pool util forest: Difference between revisions
described deltas |
|||
| Line 2: | Line 2: | ||
==Class Tracker== | ==Class Tracker== | ||
Number of dictionaries that store the shares in various ways to allow fast access. | Number of dictionaries that store the shares in various ways to allow fast access. | ||
# | |||
# | This class is critical for performance. It stores and updates '''Deltas''' that are used for quickly answering queries by caching data between two points in the sharechain. Each share (item) has a delta that goes between it and its highest parent and contains information such as how much work was done and how many shares are in between. If the highest parent has its parent added, the delta will keep referring to the old highest parent until it is next needed, and then it will be updated. | ||
# deltas ( | |||
# reverse_deltas (ref -> set of | Normally this class stores shares. These are called items in the code. I guess this is because the class is reused elsewhere? | ||
# items (hash->item) Since share(item) contains parent share allows you to link to previous shares all the way to the tail. | |||
# reverse (delta.tail->set of item_hashes) Allows you to link share to the next share that came after it all the way to the head. | |||
# deltas (item_hash -> delta, ref) | |||
# reverse_deltas (ref -> set of item_hashes) | |||
# delta_refs (ref -> delta) | # delta_refs (ref -> delta) | ||
# reverse_delta_refs ( delta.tail -> ref) | # reverse_delta_refs ( delta.tail -> ref) | ||
===Method add=== | ===Method add=== | ||
Adds a share to the tracker | Adds a share to the tracker | ||
Revision as of 15:58, 9 July 2012
This contains code for tracking shares.
Class Tracker
Number of dictionaries that store the shares in various ways to allow fast access.
This class is critical for performance. It stores and updates Deltas that are used for quickly answering queries by caching data between two points in the sharechain. Each share (item) has a delta that goes between it and its highest parent and contains information such as how much work was done and how many shares are in between. If the highest parent has its parent added, the delta will keep referring to the old highest parent until it is next needed, and then it will be updated.
Normally this class stores shares. These are called items in the code. I guess this is because the class is reused elsewhere?
- items (hash->item) Since share(item) contains parent share allows you to link to previous shares all the way to the tail.
- reverse (delta.tail->set of item_hashes) Allows you to link share to the next share that came after it all the way to the head.
- deltas (item_hash -> delta, ref)
- reverse_deltas (ref -> set of item_hashes)
- delta_refs (ref -> delta)
- reverse_delta_refs ( delta.tail -> ref)
Method add
Adds a share to the tracker