Bug 908745

Summary:	RFE: change VdsRefreshTimeout to 3 seconds
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Yaniv Kaul <ykaul>
Component:	ovirt-engine	Assignee:	Eli Mesika <emesika>
Status:	CLOSED ERRATA	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, bazulay, dyasny, iheim, jkt, lpeer, oramraz, pstehlik, Rhev-m-bugs, sgrinber, yeylon, ykaul, yzaslavs
Target Milestone:	---	Keywords:	FutureFeature, Improvement
Target Release:	3.2.0	Flags:	dyasny: Triaged+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	infra
Fixed In Version:	sf8	Doc Type:	Enhancement
Doc Text:	--no tech note required	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-06-10 21:47:30 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	915537

Description Yaniv Kaul 2013-02-07 12:23:00 UTC

Description of problem:
The current value of 2 seconds is a bit low. The UI refreshes every 5 seconds.
I've changed it to 4 seconds on my setup (from the default 2). The setup has ~13 hosts, 9 of which active, and it reduced the CPU load on my RHEVM by ~40-50%.
I'm sure DB IO has also been reduced, did not measure it though.

Need to think if on upgrade we should change the value as well.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Barak 2013-02-10 10:58:33 UTC

why not 4 ?

Comment 6 Eli Mesika 2013-02-10 14:21:39 UTC

fixed in commit : ccb5257

Comment 8 Oded Ramraz 2013-03-03 20:06:08 UTC

[root@aqua-rhel yum.repos.d]# rhevm-config -g VdsRefreshRate
VdsRefreshRate: 3 version: general


Verified sf9

Comment 9 Cheryn Tan 2013-04-03 06:51:43 UTC

This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.

* Consequence: What happens when the bug presents.

* Fix: What was done to fix the bug.

* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes

Thanks in advance.

Comment 10 errata-xmlrpc 2013-06-10 21:47:30 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHSA-2013-0888.html