Hi,
I'm trying to enumerate all the daemon threads VDSM uses, as in 4.15.0
(to be exact, as in master 3228f5dad8f488192ea62f4e3e39172832435e80)
So far I got:
===
SocketServer: 1 service, short lived thread per request?
VDSM alone, with no VM running
num whatwhere
On Fri, Jul 04, 2014 at 06:09:44AM -0400, Francesco Romani wrote:
Hi,
I'm trying to enumerate all the daemon threads VDSM uses, as in 4.15.0
(to be exact, as in master 3228f5dad8f488192ea62f4e3e39172832435e80)
So far I got:
===
SocketServer: 1 service, short lived thread per request?
Hi,
Nir has begun reviewing my draft patches about the thread pool and sampling
refactoring (thanks!),
and already suggested quite some improvements which I'd like to summarize
Quick links to the ongoing discussion:
http://gerrit.ovirt.org/#/c/29191/8/lib/threadpool/worker.py,cm
- Original Message -
From: Francesco Romani from...@redhat.com
To: devel@ovirt.org
Sent: Friday, July 4, 2014 1:09:44 PM
Subject: [ovirt-devel] [VDSM] VDSM threads as in vdsm 4.15.0
Hi,
I'm trying to enumerate all the daemon threads VDSM uses, as in 4.15.0
(to be exact, as in
- Original Message -
From: Francesco Romani from...@redhat.com
To: devel@ovirt.org
Sent: Friday, July 4, 2014 5:48:59 PM
Subject: [ovirt-devel] [VDSM][sampling] thread pool status and handling of
stuck calls
Hi,
Nir has begun reviewing my draft patches about the thread pool