Back
The database had a lot of free pages due to a large number of row deletes over time. The Laravel Pulse package was the main cause of these deletes (recording entries and then deleting them after a period), but cache, jobs, etc also contributed to the free space that could be truncated off the file.
•
Interesting indeed, do you mean that you've been working with laravel pulse using sqlite database?
•
Yes. Pinkary is currently using Laravel Pulse, saving entries to the production database (which is sqlite).
•
Why not create Second separate database only for pulse 🤔. I am using separate database for my product which gets around 1M requests per day and i can imagine how much does it affect production database. I am still logging each and every request and not using sampling.
•
I think exactly this way, I use a separate database in production for pulse...
I'm curios how big is your pulse db with that amount of traffic
Check out www.sqlite.org/lang_vacuum.html and blogs.gnome.org/jnelson/2015/01/06/sqlite-vacuum-and-auto_vacuum for more info.
