Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352720 - Performance in object mapping
Summary: Performance in object mapping
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: UI (show other bugs)
Version: 1.0.0   Edit
Hardware: PC Windows XP
: P2 critical (vote)
Target Milestone: Indigo SR1   Edit
Assignee: Markus Tiede CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-21 05:31 EDT by Felix Ziesel CLA
Modified: 2011-09-15 06:03 EDT (History)
2 users (show)

See Also:

Attachments
Eclipse for Testers project (226.76 KB, application/zip)
2011-07-21 05:31 EDT, Felix Ziesel CLA 		no flags Details
Validated by comparing version 5.1.00155 to the current version of August 25th. (40.00 KB, application/msword)
2011-08-25 11:03 EDT, Felix Ziesel CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Ziesel CLA 2011-07-21 05:31:41 EDT 
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.
Comment 1 Felix Ziesel CLA 2011-07-21 05:38:27 EDT 
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.
Comment 2 Markus Tiede CLA 2011-08-18 10:38:04 EDT 
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.
Comment 3 Felix Ziesel CLA 2011-08-25 11:03:01 EDT 
Created attachment 202155 [details]
Validated by comparing version 5.1.00155 to the current version of August 25th.
Comment 4 Alexandra Schladebeck CLA 2011-09-09 05:08:15 EDT 
After speaking to Felix - his last comment was the retest. The bug can be closed.