Bug 882 - Saving imported project taking an extremely long time
Summary: Saving imported project taking an extremely long time
Status: VERIFIED FIXED
Alias: None
Product: Identity Designer
Classification: Identity Manager
Component: Schema Management (show other bugs)
Version: 1.0.0 Designer
Hardware: x86 Other
: P5 - None : Major (vote)
Target Milestone: 1.0 M2.1
Assignee: Drew Chamberlain
QA Contact: Michael Dean
URL:
Whiteboard:
Keywords: Built, Provo
Depends on:
Blocks: 478
  Show dependency tree / graph
 
Reported: 2005-01-07 20:55 UTC by Marvin Dean
Modified: 2011-06-05 01:09 UTC (History)
0 users

See Also:
Found By: Integration Test
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
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 Marvin Dean 2005-01-07 20:55:06 UTC 
This has just been intoduced with the latest milestone integration builds.

To dupe use my tree:
import mydriverset from madean2.provo.novell.com
admin.novell
junk
make a small change and then save it.  Then take a nap.....
Comment 1 Will Peterson 2005-01-10 21:05:06 UTC 
Marv,

Can you try removing your configManifest and see if that makes the process go
faster.  The only thing I can see that is strange here is taht you have a HUGE
config manifest.

Thanks.
Comment 2 Will Peterson 2005-01-10 21:09:07 UTC 
Actually it's your application schema attribute, sorry.
Comment 3 Will Peterson 2005-01-11 18:28:23 UTC 
Schema tools needs to load and store schema as EMF objects, instead of a string.
 This will resolve the performance issues that are related to this bug.
Comment 4 Drew Chamberlain 2005-01-12 20:27:11 UTC 
These comments are from Bill-  Our current priorities are 
functionality not performance.  There is also too much risk 
in working on this for Milestone 2
Comment 5 Marvin Dean 2005-02-07 23:05:37 UTC 
Small performance issues can be overlooked, however, extremely visible
performance issues appear to break us.  This issue caused my workstation to lock
up for about 10 minutes to wait for import to complete and caused 100% CPU
utilization on both linux and windows.  I think this should be addressed in 2.1.
 Bill what do you think.
Comment 6 Bill Street 2005-02-17 00:56:38 UTC 
This is fixed for now.  Drew put in a limit of schema to 200k for m2.1  We will
fix for real in the future implementation of schema.
Comment 7 Howard Vanfleet 2005-02-18 23:50:25 UTC 
Included in Designer build 20050218
Comment 8 Bill Street 2005-09-16 21:31:45 UTC 
Adding built keyword.
Comment 9 Bill Street 2007-04-30 16:37:27 UTC 
Marking closed/resolved fixed bugs public view.
Comment 10 Bill Street 2007-04-30 16:40:03 UTC 
Marking closed/resolved fixed bugs public view.