Response time worsens when using shrinkwrap

[SI_10623722]

In models that use a lot of shrinkwrap, there is a considerable wait time when opening and operating files.
Due to the assembly structure, it is not possible to completely eliminate shrinkwrap.
I have attached a sample model, so I would appreciate your advice on improving the operation.
The sample model is a simple one created for verification purposes. In the actual model, "opening a file" takes about 4 minutes, and other operations take even longer. Also, the operations in the question are only representative ones, and in reality there are many other operations.
It would be even better if I could improve it by upgrading my PC's specs. Which parts of my PC should I upgrade? The graphics card, the memory?

[StephenW]

Your computer specs look reasonable. When you are loading your assembly, check your RAM usage and if you aren't running out of RAM, you are good there.

Your attachment is just a spreadsheet and not models, did you intend to include models?

It's possible your shrinkwrap models are just huge, too much detail or ?? Are these surface shrinkwraps or solids?

Can you dumb down the detail in your shrinkwraps?

I would suggest utilizing simplified reps and not having the shrinkwrap in memory unless absolutely necessary. 

[SI_10623722]

Thank you for your quick response. The data was too large to upload, so I split it into two and uploaded it now. Here is the first part.

[SI_10623722]

Second, unzip both files, put them in one folder, then open the assembly in master. Thank you.

[MartinHanak]

Hi,

just FYI ... if you ask Creo to open an assembly then Creo write information similar to following one into trail file.

~ Command `ProCmdRecentFileOpen`  `E:\\users\\creo9_parametric\\rr_2019-02-21\\asm0001.asm`
!Command ProCmdModelOpenExe was pushed from the software.
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\asm0001.asm.7
!LIGHT_FIX_MODEL_RMODE is 51
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\p1.prt.11
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\p1.prt.11
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\p2.prt.10
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\p2.prt.10
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\p3.prt.9
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\p3.prt.9
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\podsestava.asm.2
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\cp_p1.prt.13
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\cp_p1.prt.13
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\cp_p2.prt.2
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\cp_p2.prt.2
!30-Oct-24 16:00:16  Start E:\users\creo9_parametric\rr_2019-02-21\cp_p3.prt.1
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\cp_p3.prt.1
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\podsestava.asm.2
!30-Oct-24 16:00:16  End   E:\users\creo9_parametric\rr_2019-02-21\asm0001.asm.7

In this listing you can find loading time of every component.

[SI_10623722]

Thank you!
I'll check it out.

[MartinHanak]

---

@SI_10623722 wrote:

Thank you!
I'll check it out.

---

Hi,

I did a short test in Creo 8.0.4.0. Below you can see results.

!22-Nov-24 16:36:00  Start E:\tmp\licence\241114_SAMPLEDATA\sm-topassy.asm.2
!22-Nov-24 16:36:16  End   E:\tmp\licence\241114_SAMPLEDATA\sm-topassy.asm.2 ... 16 seconds (2.2 GB RAM allocated)

!22-Nov-24 16:39:33  Start E:\tmp\licence\241114_SAMPLEDATA\sm-ha-00.asm.4
!22-Nov-24 16:39:45  End   E:\tmp\licence\241114_SAMPLEDATA\sm-ha-00.asm.4 ... 12 seconds

!22-Nov-24 16:39:33  Start E:\tmp\licence\241114_SAMPLEDATA\sm-ga-00_shr.prt.1
!22-Nov-24 16:39:40  End   E:\tmp\licence\241114_SAMPLEDATA\sm-ga-00_shr.prt.1 ... 7 seconds

!22-Nov-24 16:39:40  Start E:\tmp\licence\241114_SAMPLEDATA\sm-pa-00_shr.prt.1
!22-Nov-24 16:39:41  End   E:\tmp\licence\241114_SAMPLEDATA\sm-pa-00_shr.prt.1 ... 1 second