----- Original Message -----
From: "Nir Soffer" <nsoffer@redhat.com> To: "Saggi Mizrahi" <smizrahi@redhat.com> Cc: "Francesco Romani" <fromani@redhat.com>, devel@ovirt.org, "Michal Skrivanek" <mskrivan@redhat.com>, "Federico Simoncelli" <fsimonce@redhat.com>, "Dan Kenigsberg" <danken@redhat.com> Sent: Sunday, July 13, 2014 1:34:50 PM Subject: Re: [ovirt-devel] [VDSM][sampling] thread pool status and handling of stuck calls
This use the current storage thread pool, but I don't think it is good enough. I think we should continue with http://gerrit.ovirt.org/29191 so we can handle stuck worker thread without decreasing the work force of the thread pool.
Hi, just a quick note until I get up to speed with last emails Since my first threadpool draft was bloated and overengineered, I restarted from scratch: https://github.com/mojaves/pyexecutor/blob/master/executor.py Now is down to 109 lines including license header and blank lines. It's on github just and only to not spam gerrit, so if anyone wish can track the evolution of the code. I'll update my gerrit patchset as soon as I have docs and tests. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani