Re: [Naviserver-users] memory bloat

[Gustaf N. (sslmail) <ne...@wu...>]

Yes, the semantics of “schedsperthread” are very similar to “jobsperthread”: when the value is 0 (default), the thread is not automatically restarted.
i have updated the documentation and added these parameters to the keyword index page.

On my wishlist, i have a dict based “database” to contain all configuration parameters with default values and help strings, which can be used to generate also various parts of the documentation automatically. This would also increase maintainability. Currently, i am quite busy with other things.

We have no search on the sourceforge pages, there are just static pages. Search engines are the best option.

all the best -g


> On 17.09.2025, at 14:19, Decent Espresso <dec...@gm...> wrote:
> 
> The default for schedsperthread and jobsperthread appears to be “0”, but I’m unclear if for schedsperthread this means “never” or “after 1 job runs” or “not relevant".
> 
> https://naviserver.sourceforge.io/n/naviserver/files/ns_schedule.html
> 
> If zero for schedsperthread means the same as it does for jobsperthread, then perhaps it means "no influence on cleaning up a thread” ?
> 
> Also, would be possible to have config parameters in the Keyword index?
> https://naviserver.sourceforge.io/n/index.html
> 
> I did not see a ‘search’ function on the docs.  Is google search the preferred way to find things?
> 
> And finally <smile> perhaps both these two parameters should be mentioned on the tuning page?
> https://naviserver.sourceforge.io/n/manual/files/admin-tuning.html