Re: [Dspam-user] Using hash storage driver - cssclean fails

[RW <rwm...@go...>]

On Wed, 20 Apr 2016 06:42:07 +0800 (PHT)
Paul Goyette wrote:

> I've got a real small set-up (two users, total of maybe 500 messages
> per day), and really have no justification for adding complexity (and
> the learning curve) for sqlite or similar.  So I'm just using the
> simple hash storage driver.

IIRC there is no learning curve for just switching to sqlite, it's just
a matter of editing the StorageDriver setting, and then rebuilding from
corpus or starting over.

There may be a bit of a learning curve to purging on sqlite, but
cssclean hasn't worked for so long that it probably never will.


> Everything seems to run fine, except for the database maintenance.  I 
> have a couple of issues with cssclean and csscompress:
> 
...
> Has anyone else seen this?  And maybe have a solution?  Indeed, is 
> anyone else even using the hash storage driver?

When I tried sqlite I immediately switched back. I like to try
different settings and that often benefits from, or even requires,
retraining from corpus. This take 2-3 minutes with the hash driver, but
over 7 hours with sqlite.

I just add anything I train with into the corpus I used for initial
training. Occasionally I trim the corpus and recreate the database.

With low-volume TOE you could probably just ignore it. My understanding
is that it's  mostly csscompress that keep the file fast, and that
works.