storj/satellite/accounting/nodetally
paul cannon ae5947327b satellite/accounting: Use metabase.AliasPiece with tally observer
We want to eliminate usages of LoopSegmentEntry.Pieces, because it is
costing a lot of cpu time to look up node IDs with every piece of every
segment we read.

In this change, we are eliminating use of LoopSegmentEntry.Pieces in the
node tally observer (both the ranged loop and segments loop variants).
It is not necessary to have a fully resolved nodeID until it is time to
store totals in the database. We can use NodeAliases as the map key
instead, and resolve NodeIDs just before storing totals.

Refs: https://github.com/storj/storj/issues/5622
Change-Id: Iec12aa393072436d7c22cc5a4ae1b63966cbcc18
2023-03-29 12:24:05 +00:00
..
node_tally_test.go satellite/accounting/nodetally: add ranged loop 2023-01-17 13:50:18 +01:00
node_tally.go satellite/accounting: Use metabase.AliasPiece with tally observer 2023-03-29 12:24:05 +00:00
ranged_loop_test.go satellite/accounting: Use metabase.AliasPiece with tally observer 2023-03-29 12:24:05 +00:00
ranged_loop.go satellite/accounting: Use metabase.AliasPiece with tally observer 2023-03-29 12:24:05 +00:00