Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352721 - Performance for saving a lot of new component names
Summary: Performance for saving a lot of new component names
Status: CLOSED FIXED
Alias: None
Product: Jubula
Classification: Technology
Component: UI (show other bugs)
Version: 1.0.0   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: Indigo SR1   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-21 05:52 EDT by Felix Ziesel CLA
Modified: 2011-09-15 06:03 EDT (History)
3 users (show)

See Also:

Attachments
Projects for reproduction (227.82 KB, application/zip)
2011-07-21 05:52 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:52:01 EDT 
Created attachment 200071 [details]
Projects for reproduction

Using an oracle db for the appended project "Eclipse for Testers".

1. Open the test case "New Test Case"
2. Set new component names for all components (they have to be different). Don´t save in between!
3. Save. This will take round about 15 seconds.
Comment 1 Markus Tiede CLA 2011-09-07 02:32:29 EDT 
This performance should have majorly increased since fixing bug 352720 - could you please verify this and / or re-open this ticket if performance is not yet good enough?
Comment 2 Alexandra Schladebeck CLA 2011-09-09 05:21:39 EDT 
The performance is now measured as around 7 seconds. I'm going to close the bug as the performance is indeed better. If however, the new value is still not sufficient, then please reopen the bug.