Bug 478 - Import is taking a very long time to complete.
Summary: Import is taking a very long time to complete.
Status: VERIFIED WONTFIX
Alias: None
Product: Identity Designer
Classification: Identity Manager
Component: Import (show other bugs)
Version: 1.0.0 Designer
Hardware: x86 All
: P5 - None : Normal (vote)
Target Milestone: FCS
Assignee: Brent Thurgood
QA Contact: Brady Rogers
URL:
Whiteboard:
Keywords: Provo
Depends on: 882
Blocks:
  Show dependency tree / graph
 
Reported: 2004-12-09 22:10 UTC by Marvin Dean
Modified: 2011-06-03 17:49 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 2004-12-09 22:10:45 UTC 
This is happening not while importing but after when it is trying to auto layout
all object on the modeler page.  Demonstrated to Lee the issue and he is working
on it.
Comment 1 Marvin Dean 2004-12-09 22:10:57 UTC 
bstreet (  9/7/2004 5:49:25 PM  Fixing - Approved for Investigation ) Lee has
implemented a fix for this for M1.  If this fix does not improve performance
then we intend to reflect the problem in the Readme and fix this for M2.
Comment 2 Bill Street 2005-01-10 23:31:58 UTC 
Brent-  Can you help with this please.  We need some guidance on where/how to
fix this and what the cause is.
Comment 3 Marvin Dean 2005-01-14 20:37:12 UTC 
Brent:
I've isolated this to certain drivers.  Seems that edir driver takes a long 
time to save and import.  It is like we are churning on some of the driver 
attributes.  You can try to import mydriverset on my madean2.provo.novell.com 
server and you will see the problem.
Comment 4 Brent Thurgood 2005-02-09 15:48:55 UTC 
This was a problem with saving the project when we had large application 
schema files, not with import.  

Marking this as WONTFIX.
Comment 5 Marvin Dean 2005-02-09 15:52:56 UTC 
I am going to change the status to duplicate and reference the other 
performance issue reported.