feat: view database size #954
Conversation
Time Submission Status
|
|
Looks good to me. Could you add test too? cc @outerlook |
|
@MicBun done |
|
Hey @MicBun @williamrusdyputra I'll just leave a note about performance on this method; I'll check if it's still true, but postgres does full table scans to yield count responses, so this means going through every row of our DB each time this is queried Doesn't mean that this isn't the best for now, but it's good to ensure we don't query too much without good caches It all depends on how much data we have, but recently is growing a lot Please react if you read so I know it's ok |
|
yes, this will be a temporary solution until we figure out how to extend 'pg' functions such as 'pg_database_size'. for now, this query will run only once a day during midnight UTC, just to keep a record. |
Related Problem
resolves: https://github.com/trufnetwork/truf-network/issues/515
How Has This Been Tested?
streams:
1 × (128 + 100) = 228metadata:
5 × (230 + 48 + 100) = 5 × 378 = 1890Total =
228 + 1890 = 2118 bytes