Opening ASM files and specially large ASM may take some time.
But... To be able to help you with your question, you should tell us a bit more details....
- How big is the ASM in part count?
- How much sub-levels are there?
- How is the folder structure?
- Are the files local or on a shared folder?
All this could influence the loading of the structure in DM.
Do you mean 8500 total parts or 8500 unique (ie. different) parts ?
If its 8500 total I wouldn't consider that a particularly big assembly.
If you mean 8500 unique parts, what is the total part count ?
Your network speed and the number of users accessing the server will also have an impact.
In the past I've seen load times reduce considerably when I've been the only user accessing the server.
You have a copy on your local drive that has similar performance results.
On this test data, have you run OpenSave on everything? I just wonder if a lot of time is being spent resolving out of date links.
I don't run OpenSave utility.
I try 1 time for another test of a similar big assembly, copied in local, but the program crash after about 1000 files.
I don't know the utility of the OpenSave of all files, but I read that is a good job to do.
I run the SESysInfo with the assembly and there are a lot of unused file .jpg (texture), but not missing files. (because a lot of files are created with previous version of solid edge and they are search in texture folder by the previous version of SE).
I searched an app for repair this unused links but I don't found it.
I can try to run OpenSave in a copy in local and then try open Design Manager and the assembly.
We also have a lot of time with open all the assembly (it takes 10 minutes) but with configuration and the options for large assembly we redused a lot time. But remain the time problem with the Save and the refresh/update assembly. They takes a lot of time. (I check the options of Refresh and Save limites to only the modified files, but there isn't a good speedup).