Upgrade memory of fly.io database
I know this maybe is not the place to ask but what is best practice for upgrading memory of fly.io database postgres? I right now have 223 mb but it somehtimes runs out of this, so maybe adding like 1gb is good? any tips on how to do this?
2 Replies
Hi @Sven. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
----------------------
While Wasp provides integration with Fly.io for deployment, the specific details of upgrading Fly.io's PostgreSQL database resources are not directly covered in the provided Wasp documentation. However, I can offer some general guidance based on the information we have:
1. Memory issues: You're correct that running out of memory can be problematic for your database. Upgrading from 223 MB to 1 GB could indeed help resolve these issues.
2. Upgrading process: The exact process for upgrading your Fly.io PostgreSQL database resources isn't detailed in the Wasp documentation. You would need to refer to Fly.io's specific documentation for this.
3. Wasp and Fly.io integration: Wasp does provide tools for deploying to Fly.io, including setting up a PostgreSQL database. As mentioned in the Fly.io deployment docs (https://wasp-lang.dev/docs/advanced/deployment/manually#flyio-server-and-database), Wasp offers automated deployment to Fly.io, which includes database setup.
4. Minimum requirements: There's an indication that more than 1 GB of memory might be necessary for smooth operation. In a Discord conversation about OpenSaaS setup, it was noted that resizing from 512 MB to 1 GB RAM resolved issues Discord thread (https://discord.com/channels/686873244791210014/1213593156646604820).
5. Checking current setup: You can use Fly.io's CLI tools to check your current database setup. Commands like
fly postgres connect -a your-app-name-db can be useful for this purpose Github Issue comment (https://github.com/wasp-lang/wasp/issues/1464).
For specific instructions on how to upgrade your Fly.io PostgreSQL database resources, I recommend consulting Fly.io's official documentation or support channels. The Wasp documentation doesn't provide direct guidance on this particular operation.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @Sven, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?@Sven Nothing special on the Wasp side, I believe your best bet is chekcing out the Fly.io documentation!