73a279235a
After infrastructure changes redis instance is not neccessay close to core instance (where tally is calculated) and round trips to get data from redis can be very costly. From less than hour calculation can take few hours for larger satellite. This change combines 'segment' and 'storage' usage requests into batches to reduce latency impact on tally calculation. https://github.com/storj/storj/issues/5800 Change-Id: I87e57ec09e88fd167060a4ed51dc8b0274a095c5 |
||
---|---|---|
.. | ||
live | ||
nodetally | ||
projectbwcleanup | ||
rollup | ||
rolluparchive | ||
tally | ||
billing_test.go | ||
bucketstats.go | ||
bucketusage.go | ||
common.go | ||
db_test.go | ||
db.go | ||
projectlimitcache_test.go | ||
projectlimitcache.go | ||
projectusage_test.go | ||
projectusage.go |