Sorry for the late reply, was a few days on a business trip.

On Wed, 30 Jul, Michael Herger wrote:

> >  > What's the file's size now?
> >
> > After VACUUM it is 2.0 GB now.
> 
> Still? Wow.

Yes, and it has grown since then to 2.1 GB again.

But I just stopped and restarted LMS. The startup was almost instant
this time, again. So it looks like the other options I changed on your
advise made a change and the large database itself wasn't responsible
for the slow startup time.

> > Perhaps this is a session setting, so that it is set within LMS but
> > not for other clients like sqlite3 cmdline tool?
> 
> No, it's one of the things you even have to define before almost 
> anything else: the reason why it didn't work was that I only defined
> it after some of the other parameters. Now I've put it really first
> thing after creating the db file.

So, I'll have to update to a later nightly build and delete the
imgproxy.db, so that it can get re-created with the auto-vacuum
activated, right?

-- 
Stefan Bellon
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta

Reply via email to