Bug 1374988 - MOM causes Vdsm to slow down, high number of 'vmGetIoTunePolicy' API calls - vdsm
Summary: MOM causes Vdsm to slow down, high number of 'vmGetIoTunePolicy' API calls - ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: vdsm
Classification: oVirt
Component: Bindings-API
Version: 4.18.15
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.0.6
: 4.18.16
Assignee: Jenny Tokar
QA Contact: Shira Maximov
URL:
Whiteboard:
Depends On:
Blocks: 1366556
TreeView+ depends on / blocked
 
Reported: 2016-09-11 12:47 UTC by Jenny Tokar
Modified: 2017-02-01 06:14 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-01-18 07:27:48 UTC
oVirt Team: SLA
Embargoed:
rule-engine: ovirt-4.0.z+
mgoldboi: exception+
mgoldboi: planning_ack+
rgolan: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1366556 0 high CLOSED MOM causes Vdsm to slow down, high number of 'vmGetIoTunePolicy' API calls 2021-02-22 00:41:40 UTC
oVirt gerrit 63748 0 master MERGED Add new api to get the IO tune policies for all vms 2020-03-08 19:23:14 UTC
oVirt gerrit 65963 0 ovirt-4.0.5 ABANDONED Add new api to get the IO tune policies for all vms 2020-03-08 19:23:14 UTC
oVirt gerrit 65964 0 ovirt-4.0 MERGED Add new api to get the IO tune policies for all vms 2020-03-08 19:23:13 UTC
oVirt gerrit 65974 0 master MERGED Update required mom version and interface 2020-03-08 19:23:13 UTC

Internal Links: 1366556

Description Jenny Tokar 2016-09-11 12:47:24 UTC 
MOM is having high performance impact on Vdsm due to high number of calls to vmGetIoTunePolicy API calls.
Comment 1 Jenny Tokar 2016-09-11 12:51:39 UTC 
This fix will contain a new vdsm api to get Io tune policies for all vms at the same api call instead of calling vmGetIoTunePolicy for each vm. 
MOM will then be able to use that api and so will reduce the load on vdsm.
Comment 2 Martin Sivák 2016-09-27 15:50:01 UTC 
This is the vdsm part of the Io QoS fix and so it should be targeted to the same release.
Comment 3 Yaniv Kaul 2016-10-30 09:18:23 UTC 
What's the status here? I see above patch is already merged to master. What about 4.0? Is this going to 4.0.5, or can it be postponed to 4.0.6?
Comment 4 Jenny Tokar 2016-11-03 12:04:00 UTC 
I though this was postponed to 4.0.6?
Anyway I can cherrypick it to 4.0.5 if needed.
Comment 5 Martin Sivák 2016-11-03 13:13:25 UTC 
It was supposed to be moved to ovirt-4.0.6.. but I see Moran gave it an exception...
Comment 6 Martin Sivák 2016-11-03 13:14:51 UTC 
Are we really considering a VDSM rebuild for 4.0.5? I thought the decision was to postpone this.
Comment 7 Shira Maximov 2016-11-29 14:04:30 UTC 
verified on :
vdsm-4.18.17-1.el7ev.x86_64

-=>>cat /var/log/vdsm/vdsm.log | grep 'getAllVmIoTunePolicies succeeded' | grep "2016-11-29 13:50" | wc -l 
4

Thread-13::DEBUG::2016-11-29 14:02:54,355::health::97::health::(_check_garbage) Collected 298 objects
Thread-13::DEBUG::2016-11-29 14:02:54,361::health::122::health::(_check_resources) user=10.62%, sys=6.15%, rss=316152 kB (+100), threads=69
Note You need to log in before you can comment on or make changes to this bug.