Reaching free limit with a very small DB
Hi, I'm using free tier with 500 MB limit. My side-project DB 2 has branches (dev which is not used and prod). It has 7 tables where only one is worth mentioning (size-wise) and it also has like 3-4k rows tops amounting to (according to DBeaver) 5.6 MB. Daily "traffic" consists of 100-200 row upserted and 100-200 rows deleted.
But now Neon notifies me that I'm reaching the 500 MB limit.
What does count against this 500 MB limit that might be so large? Indexes - I have very few simple ones, I'd say negligible.
Many thanks.
3 Replies
extended-salmonOP•5mo ago
Well I fund out that I can disable instant restore in Neon console that helps a bit, but it's still occupying 320 MB which I really still don't understand.
environmental-rose•5mo ago
Storage is your data + history. As mentioned above, the first thing to try is decreasing your restore window. It's one day by default. All of your database changes (writes) are logged in your history for point in time restore, adding to storage.
https://neon.tech/docs/manage/projects#configure-your-restore-window
If you use branches, the downside of reducing your restore window is that your branches will add to storage as soon as they fall out of your restore window.
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....
extended-salmonOP•5mo ago
@Daniel thanks, yes I did that. But I still don't understand what's occupying the space if I have set the Instant restore to 0h (that I assume completely disables the WAL).