Total indexed CIDs on landing page is incorrect #17
Comments
masih
added a commit
that referenced
this issue
Jun 8, 2023
In order to avoid confusion, do not show the "Total CIDs Indexed" count until there are services in place that reasonably accurately can report it. Relates to: - #17
masih
added a commit
that referenced
this issue
Jun 8, 2023
In order to avoid confusion, do not show the "Total CIDs Indexed" count until there are services in place that reasonably accurately can report it. Relates to: - #17
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The total number of CIDs indexed fluctuates based on which backend serving stats. The calculation itself is dependant on the datastore used to store information: not all KV stores offer accurate count of unique keys due to performance reasons. A solution needs to be specifically designed to keep track of unique CIDs indexed that at the same time does not impact the ingest throughput due to locking etc.
An example of such solution is to keep atomically incremented numbers based on CID prefix, then periodically aggregate them to get a total.
In the meantime, remove the count from the landing page to avoid confusion.
Cc @TorfinnOlsen
The text was updated successfully, but these errors were encountered: