Advanced settings
When your app runs slowly or hits high-load notices, find and optimize slow queries before paying to resize your server. If your app genuinely outgrows its limits, you can increase processing capacity or storage directly in database settings.
Anyone whose app feels sluggish under traffic, receives high-load alerts, or is running out of database disk space.
Do this, in order
- 1
Go to More, click Database, select Manage, then open Settings to check the CPU, Memory, and Disk cards for recent pressure.
This reveals whether your database actually hit its hardware limits in the past 24 hours.
- 2
Ask Lovable in chat to run a health check and optimize your slowest queries.
Inefficient database requests are usually the real cause of slowdowns, and fixing them saves you from paying for a larger server.
- 3
Increase database storage under Database settings if your disk space is nearly full.
Running out of disk space prevents data from saving, but this setting is separate from processing power.
- 4
Select a larger instance size under Database size (or ask Lovable to resize it on Pro plans) only if queries are optimized and traffic remains high.
Larger database instances handle more simultaneous traffic but consume more credits every hour your app runs.
Paste this into your project
My app feels slow. Run a health check on my database, find the slowest database queries, and optimize the worst ones.
Words decoded
- query
- A specific command sent to your database to search for, add, or update information.
- instance
- The virtual computer server dedicated to running your database.
- index
- An organized lookup list created in your database that lets it find records much faster.
Where people get stuck
- Upgrading your database size before fixing slow queries will increase your hourly credit cost without solving the root problem.
- Database storage space can only be increased, never decreased.
- Free plans are locked to the Tiny instance size and require a paid plan to resize.
- Resizing causes a brief service interruption while the database restarts.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.