Self-Hosted Docker. Resources utilization #26159
Unanswered
MaxGrekhov
asked this question in
Questions
Replies: 3 comments 1 reply
-
@MaxGrekhov Any findings on this ? |
Beta Was this translation helpful? Give feedback.
1 reply
-
please any solution to this |
Beta Was this translation helpful? Give feedback.
0 replies
-
Please any update on this |
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
-
I saw news about GA and a lot of buzz around Supabase lately so I decided to look at it. I work for an enterprise, and Supabase could be a way for small\mvp projects for new clients. I followed the "self-hosted docker" instructions and got the base setup. I tested performance, and it's 3-5x slower than manual implementation, which is ok for such a tool. However, I'm confused by resource usage. Docker compose stats under no load after a couple of API tests:
RAM:
~3.1GB API gateway (kong) + analytics
~0.9GB everything other including CORE functionality
Total: ~4GB
Why do the requests router with a couple of plugins and analytics module consume so much RAM?
I googled Kong memory consumption and faced so many "leaking" issues. From a personal perspective, I would replace it instantly.
I didn't investigate analytics, but it looks quite "expensive" on RAM for analytics, although not as Kong.
Am I missing something?
Beta Was this translation helpful? Give feedback.
All reactions