The Pinkary database just went from ~800MB to ~90MB.
How?
VACUUM;
🤯
The Pinkary database just went from ~800MB to ~90MB.
How?
VACUUM;
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.
Yup! This has been discussed as an option. Good minds think alike!
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
According to the docs, sqlite is not supported. I tried it myself in a hobby project. I got some errors open the Pulse dashboard. How did you manage that?
Ah. I think that's a mixup with the docs. It appears the accepted drivers are
['mariadb', 'mysql', 'pgsql', 'sqlite']
Nice to hear. I did a little code diving. The error I get, is from a thrid party card. So I guess it's not a Pulse problem in general. The 3rd party card uses a raw query with a sql function not available in sqlite.