Re: [ovirt-devel] [VDSM] VDSM threads as in vdsm 4.15.0

----- Original Message ----- We don't have such thread, nor short lived threads per requests (but see bellow) This is not a thread - you mean the pool of threadPool.WorkerThread I guess you mean storageServer.ConnectionMonitor thread This thread lives only during startup and does not exists when vdsm is ready. There is also ksm.KsmMonitorThread This is not a thread, don't let the interface confuse you :-) The start() method starts the bindings threads and the protocol detector you list bellow. This is another short lived thread the exit when running vms are recovered and does not exists when vdsm is ready. This thread create short living threads for each request, without any limit. If you send 100 requests, vdsm will start 100 threads the handle the requests. (since Jun 11) This server create new thread per connection. Since ovirt-3.4. This thread is long living since we use keep-alive (since 3.4). There is no limit to the number of connection threads. On and idle machine we see 3-4 such threads. So you should add 4 to the baseline for these. There is no such thread - you counted it in XmlRpcServer. When domain monitor changes state, it starts a new thread for notifying observers and this thread may start new thread for each notification. These thread exit after the notifications are done. These run on all hosts but the spm These run only on the spm - so we have only pool_size / 2 mailbox threads. You don't need iso domain, so minimum is 1 storage domain thread. But the minimum is not interesting - we have customers with 30-40 domains, so assume 40 of these threads. Based on my corrections: 14 long living threads 10 task threads 5 mailbox threads 3-? xmlprc connection threads or ? jsonrpc requests threads 1-40 domain monitor threads 0-600 vm threads (2 per vm) Total: 33-? Nir