Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1415647 - [scale] - lower network resources comparing to 4.0
Summary: [scale] - lower network resources comparing to 4.0
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.1.0.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nobody
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-23 10:45 UTC by Eldad Marciano
Modified: 2017-01-23 11:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-23 11:02:49 UTC
oVirt Team: Infra


Attachments (Terms of Use)

Description Eldad Marciano 2017-01-23 10:45:08 UTC
Description of problem:
in part of scale up 4.1 testing we found lower rate of network sent recv bytes.

I submit this as a bug in order to make sure that anything didn't broken.

we need to clarify if some changes made around: 
- engine db queries results set. 
- engine db queries invocations (caching).
- vdsm api calls results set
- vdsm api invocations (caching)

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

How reproducible:
100%

Steps to Reproduce:
1. scale up scenario of 1 host 1 SD and ramp up of 111 vms.
2. monitor the env for 12 hours.

Actual results:
lower network traffic were monitored

Expected results:
we expect to have better performance for build to build.
currently we suspect that lower rate as a bug and not as enhancement.

Additional info:

Comment 2 Yaniv Kaul 2017-01-23 11:02:49 UTC
Closing. There's hardly anything we can do with this bug.
There were tens, if not more of changes performed.
For example, the 4.1 SDK is compressing by default, while 4.0 doesn't - did you use 4.1 SDK against 4.1 and 4.0 SDK against 4.0? (this is just an example, I believe you are using direct REST - which also, depending on the client, may or may not compress).


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