Excessive storage space used by Supabase Docker #6910
Unanswered
SyedHaizal
asked this question in
Q&A
Replies: 2 comments
-
|
older version of supabase realtime, used to generate a huge number of logged rows every minute you can check the row counts to see if this is still the case, i believe newer versions, removed this, but i dont know which version you are using |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
just clear the logs table in __analytics |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I am currently facing an issue where my locally hosted Supabase instance is using an excessive amount of storage of over 750GB. The instance is running inside a Proxmox VM on Ubuntu 24.04 LTS, managed through Coolify.
Running the size check and bloat check commands from the documentation gave the following output:
size check:
bloat check:
The rest of the bloats is less than the 1912kb.
The screenshot below shows the output of du -h of the Supabase Docker file.
I have tried the Vacuum operation as suggested by the documentation, but it only reduce the size storage slightly.
We believe the total space used by Supabase should be at maximum at around 30GB including the space of the Storage objects. Currently I am unsure if this is an issue with Supabase or Proxmox itself. How can investigate this further?
Beta Was this translation helpful? Give feedback.
All reactions