I would not consider that to be normal. But to be honest I also never did a
real benchmark on this.
Zim uses threads mostly to make IO a bit more responsive, but those should
threads should be short lived and you would not see many of them in
One thing to try is to also check the open file handles and see if there
are so many of them for zim as well.
Of course there might be a bug in cleaning up threads that could cause them
to remain active. Would be worth while to look into. Can you share with me
how you log the number of open threads?
On Fri, Oct 24, 2014 at 4:06 PM, mario@tiscali <mbe...@tiscali.it> wrote:
> I run zim-wiki 0.62 on RedHat Linux 6.5. Happily.
> Lately my system started experiencing strange "fork failed - resource
> temporarily unavailable" problems that I see as unrelated to zim-wiki.
> Still, trying to diagnose these, I noticed that running a single instance
> of zim-wiki consumes, on my system, 110 linux threads (under the same
> process). It is the heaviest thread consumer on my system.
> Should I consider this normal?
> This is with python 2.6.6 (r266:84292).
> Thanks in advance,
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : email@example.com
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~zim-wiki
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~zim-wiki
More help : https://help.launchpad.net/ListHelp