Bug 1702397 - RFE: investigate using one thread per connection for tick/poll
Summary: RFE: investigate using one thread per connection for tick/poll
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Virtualization Tools
Classification: Community
Component: virt-manager
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Cole Robinson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-23 16:46 UTC by Cole Robinson
Modified: 2020-09-11 20:57 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-11 20:57:31 UTC
Embargoed:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.