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.
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