Hi Jesse,

> I am going to give ovsqlite another try. I was reading through the
> man page and configuration file, paying attention to this recommendation:
>
> A transaction occurs every transrowlimit articles or transtimelimit
> seconds, whichever is smaller. You are encouraged to keep the default
> value for row limits and, instead, adjust the time limit according to
> how many articles your news server usually accepts per second during
> normal operation (you can find statistics about incoming articles in
> your daily Usenet reports).
> Inserting or deleting a database row within a transaction is very fast
> whereas committing a transaction is slow, especially on rotating
> storage. Setting transaction limits too low leads to poor
> performance. When rebuilding overview data, it may be worth
> temporarily raising these values, though.
>
> Do you recommend increasing both transrowlimit and transtimelimit? I am also
> looking at the pagesize and cachesize parameters.

When testing on my news server, which is a relatively fast VPS, I did
not notice any change with a x10 to transrowlimit or transtimelimit
during an overview rebuild.
This recommendation comes from the implementer of ovsqlite, and I
believe it may be useful on slower systems (with rotating hard drives or
slow CPU).

I kept the defaults for pagesize and cachesize. I'm not an SQLite
expert, and ovsqlite is fast enough in my testing news server. Of
course if you find out tweaks that make it even faster in your news
server, feel free to share and I'll be happy to add them in our
documentation for other users.

--
Julien ÉLIE

« La médecine est un métier dangereux. Ceux qui ne meurent pas peuvent
vous faire un procès. » (Coluche)