Feature request - a day-by-day storage usage chart
It would be awesome if we could have a day-by-day storage usage chart to follow the daily usage, then we know how is it reducing/increasing.
Below is a sample chart from MotherDuck
3 Replies
genetic-orangeOP•5mo ago
Hi @NeonDevRel team, could you check this ? My storage is growing so fast, now I don't know which table causes it and I also have no idea which day does it begin to grow fast.
jolly-crimson•5mo ago
Hi @dUcK With that data size, I assume you're on a paid plan. I recommend reaching out to support for assistance:
https://console.neon.tech/app/projects?modal=support
Storage has two components: Actual data size + a history of writes that enables point-in-time restore.
You could run a query on your databases like this one to check/monitor your actual data size by table:
SELECT
schemaname '.' relname AS table_name,
pg_size_pretty(pg_total_relation_size(relid)) AS total_size,
pg_size_pretty(pg_relation_size(relid)) AS table_size,
pg_size_pretty(pg_total_relation_size(relid) - pg_relation_size(relid)) AS index_size
FROM pg_catalog.pg_statio_user_tables
ORDER BY pg_total_relation_size(relid) DESC;
For the history component, you could adjust your restore window to reduce your history size (at the risk of having a smaller restore window):
https://neon.tech/docs/manage/projects#configure-your-restore-window
Reducing your history window might be a temporary way to keep storage in check until you connect with the Neon support team.
https://neon.tech/docs/manage/projects#configure-your-restore-window
If you can wait a little, I recommend getting in touch with the Neon support team first, though.
Neon
Manage projects - Neon Docs
With Neon, everything starts with the project. It is the top level object in the Neon object hierarchy. A project can hold as many branches, databases, and roles as your application or workflow needs....
genetic-orangeOP•4mo ago
Thank you @Daniel