Bug 1337229

Summary:	performance issues with QoS
Product:	[oVirt] mom	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	Core	Assignee:	Jenny Tokar <jtokar>
Status:	CLOSED DUPLICATE	QA Contact:	Shira Maximov <mshira>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	0.5.1	CC:	bugs, mshira
Target Milestone:	ovirt-4.1.0-alpha	Flags:	michal.skrivanek: ovirt-4.1? michal.skrivanek: planning_ack? michal.skrivanek: devel_ack? michal.skrivanek: testing_ack?
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:	2016-09-27 15:43:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1337228, 1343960
Bug Blocks:

Description Michal Skrivanek 2016-05-18 14:40:21 UTC

iotune QoS is using a problematic design requiring excessive use of vdsm (and libvirt) API calls
It can be done more effectively if we take few assumptions (maybe specific to vdsm, but still worth it)

There is no need to query and set policy and values periodically, no one can change the policy without engine and vdsm knowledge.
Changes can be reported as part of VM stats if needed, one field serving as a trigger would be ok. Since VM stats is being queried by mom already there would be no need for any additional calls in stable conditions.

I'm not sure about networking QoS

Comment 1 Martin Sivák 2016-09-27 15:43:20 UTC


*** This bug has been marked as a duplicate of bug 1366556 ***