Bug 1404610
| Summary: | [downstream clone - 4.0.7] [tracker] oVirt UI / Internet Explorer performance improvements | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | rhev-integ | ||||
| Component: | ovirt-engine | Assignee: | Vojtech Szocs <vszocs> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Pavel Novotny <pnovotny> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | unspecified | CC: | awels, bugs, eberman, gklein, lleistne, lsurette, mgoldboi, oourfali, pnovotny, pstehlik, rbalakri, Rhev-m-bugs, s.kieske, srevivo, ykaul | ||||
| Target Milestone: | ovirt-4.0.7 | Keywords: | Performance, ZStream | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 1378935 | Environment: | |||||
| Last Closed: | 2017-03-16 15:30:35 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1378935 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
rhev-integ
2016-12-14 09:03:39 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release. (Originally by rule-engine) > Status: POST → MODIFIED
This bug was originally meant to collect all kinds of post-memory-leak-fix improvements.
Currently, it has 4 IE-specific patches associated. None of them is merged into master, so moving back to POST.
If we wish to proceed with those 4 IE-specific patches (only), maybe we should rename this bug.
(Originally by Vojtech Szocs)
All IE-specific patches verified on local Engine (master) build using IE11 / Windows 8.1 (thanks to Pavel Novotny). (Originally by Vojtech Szocs) (In reply to vszocs from comment #2) > Currently, it has 4 IE-specific patches associated. None of them is merged > into master, so moving back to POST. > > If we wish to proceed with those 4 IE-specific patches (only), maybe we > should rename this bug. Relevant patches are merged in master, updated BZ title. (Originally by Vojtech Szocs) All the relevant (4) patches are already merged in `ovirt-engine-4.0` branch. When verifying this bug, please check if there aren't any UX regressions, related BZs are following: * https://bugzilla.redhat.com/1160774 * https://bugzilla.redhat.com/1255428 Verified in rhevm-4.0.7.4-0.1.el7ev.noarch Browser: Internet Explorer 11 @ Windows 8.1 Pro (4 vCPU, 8 GB RAM) RHEVM environment: 1 DC, 2 clusters, 1 host, 2 NFS storages (1 data, 1 export), 41 VMs (blank, w/o OS installed, 4 of them Up). I ran a test in a loop, where it went through the main tabs and then opened & closed the New VM dialog. After each pass I wrote down the memory usage from Developer Tools / Memory / Profiling session - Process memory usage (private bytes). I compared the data against the latest release rhevm-4.0.6.3-0.1.el7ev, see the chart attached. With 4.0.6, the maximum I managed to run was 6 passes before reaching a RAM usage ~1.6 GB. This seems to be the browser limit, where it becomes unresponsive beyond usability and the app. eventually freezes or crashes. The 6 passes took 43 minutes (indeed). With 4.0.7, I managed to run 9 passes before reaching the 1.6 GB RAM usage. To compare with 4.0.6, 6 passes took 13 minutes. All 9 passes took 19 minutes. Created attachment 1259243 [details]
IE11 - webadmin memory usage chart
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. https://rhn.redhat.com/errata/RHBA-2017-0542.html |