Bugzilla – Full Text Bug Listing
| Summary: | Performance in object mapping | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Technology] Jubula | Reporter: | Felix Ziesel <Felix.Ziesel> | ||||||
| Component: | UI | Assignee: | Markus Tiede <markus.tiede> | ||||||
| Status: | CLOSED FIXED | QA Contact: | Oliver Goetz <Oliver.Goetz> | ||||||
| Severity: | critical | ||||||||
| Priority: | P2 | CC: | alexandra.schladebeck, testautomatisierung | ||||||
| Version: | 1.0.0 | ||||||||
| Target Milestone: | Indigo SR1 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows XP | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
There is a bigger customer project that has longer timeouts (10 seconds for mapping (with 100mbit network)) and saving takes some minutes. Therefore I will set this bug to critical. The major performance issues should enhance with http://git.eclipse.org/c/jubula/org.eclipse.jubula.core.git/commit/?id=aea94889109bc9830bbca9afa134e0f29eb82c7d Using the given reference project and actions I have been able to verify the lack of performance - my current timing measurement (after applying the fix) lead to: - mapping of two components: ~500 ms - saving the OME: ~5s In addition to that the save operation for multiple mappings should scale much better now. Please do not hesitate to re-assign / re-open this issue. Created attachment 202155 [details]
Validated by comparing version 5.1.00155 to the current version of August 25th.
After speaking to Felix - his last comment was the retest. The bug can be closed. |
Created attachment 200070 [details] Eclipse for Testers project Use the extended example to reproduce the issue. You need an oracle db. 1. Open "Eclipse for Testers" Project 2. Open the object mapping and map all component without saving in between 3. Save In this small example the mapping of two components could take 2-3 seconds, saving all (13) components take round about 10 seconds.