A Problem with the Supabase Shared Pooler Egress in the free plan using Prisma ORM
im seeing for a solution for this problem that i don't know how to fix it since in just 7 days it used 27% of it and im the only one using it while testing,
Im Building an App of chatbots where the messages are in a local database on the user device, when a user create a chatbot it saves it in the supabase database that is PostGreSQL with Prisma ORM, and when someone else want to chat with it, it downloads it that is the only Egress since i have the sync to the database for the messages but i turn it off and i didn't used any other device for import the sync, the sync is in a bucket and the messages are compressed with Brotli at maximum, the Supabase database is connected with the website on Vercel (the sync don't go trough Vercel but directly to the Database), what i have to still optimize it or fix this problem?
I looked at everything and i don't know what it could be the problem since it's my first time using Supabase too.