cache archive size, # of peers periodically

[okdistribute]

Every time we fetch the # of peers and the archive size of a dat, we want to be able to cache them on disk so that users can sort and search and filter by these parameters.

• Should we create other field(s) in the 'dat' table in the database for storing these stats?
• Any other stats you can think of?
• This is an opportunity to think critically about the database before we launch and users start adding themselves and their dats.

[clkao]

I think it makes sense to cache last_known_stats: {archive_size, peers, timestamp}

But I am not sure if this should be in the primary db or some secondary cache.