Bug 1702397

Summary: RFE: investigate using one thread per connection for tick/poll
Product: [Community] Virtualization Tools Reporter: Cole Robinson <crobinso>
Component: virt-managerAssignee: Cole Robinson <crobinso>
Status: CLOSED DEFERRED QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: berrange, crobinso, gscrivan
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-09-11 20:57:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Cole Robinson 2019-04-23 16:46:14 UTC 
From here: https://bugzilla.redhat.com/show_bug.cgi?id=1698088

When connected to multiple connections, if one conn is very slow it will delay UI stats reporting for all other connections, even if those connections are quick. This is because internally we use a single thread and queue for stats poll requests or object list update requests: a slow conn processing a request can back up the queue.

Also it's worth investigating how hard it is to have one thread per conn subsystem, so a thread for domains, pools, networks, interfaces, nodedevs, etc.
Comment 1 Cole Robinson 2020-09-11 20:57:31 UTC 
This is still valid to do but I don't plan to do it anytime soon, so closing