Back

The Pinkary database just went from ~800MB to ~90MB.

How?

VACUUM;

🤯

4 • •

2K

•

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.

1 • •

956

•

Interesting indeed, do you mean that you've been working with laravel pulse using sqlite database?

1 • •

471

•

Yes. Pinkary is currently using Laravel Pulse, saving entries to the production database (which is sqlite).

3 • •

402

•

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.

3 • •

479

•
In response to @talha

I think exactly this way, I use a separate database in production for pulse...

• •

164

•
  • No matching results...
  • Searching...

/ 1000