AnsweredAssumed Answered

Why is Pack and Go Slow?

Question asked by Keaton Warn on Jun 19, 2018
Latest reply on Jun 22, 2018 by Keaton Warn

When using Pack and Go, sometimes it completes the operation quickly and other times slowly. From my experience this seems to be related to the number of SW files in the directory folder of the model/drawing being Pack and Go'd. Is there a way to reduce the time it takes to complete the Pack and Go operation?

 

The specific task is running Pack and Go on an assembly with drawings to a .zip folder. All task instances are run on SW files on the LAN and saved to the local location C:\temp.

 

It is worth noting that my local drive is an SSD while the LAN is 1 gigabit and on discs.

 

Control:

•The control assembly has 8 total files and only a few unrelated document files in the test folder directory on my employee network partition. It takes less than five           seconds to Pack and Go.

 

Large LAN Directory:

•The first comparison assembly has 1 part and 1 drawing file, but the engineering directory folder they are in has over 2400 SW files (2.1 GB). It takes 50 seconds to          Pack and Go.

•The second comparison assembly has 1 part and 1 drawing file, but is in the same directory of 2400+ SW files. It takes 50 seconds to Pack and Go.

•The third comparison assembly has 18 part files, 1 assembly file, and 12 drawing files in the same directory of 2400+ SW files. It takes 54 seconds to Pack and Go.

•The fourth comparison assembly has 43 part files, 3 assembly files, and 23 drawing files in the same directory of 2400+ SW files. It takes 72 seconds to Pack and Go.

 

Small Local Temporary Directory:

•The first comparison assembly (1 part, 1 drawing) in its own local directory folder (2 total files) took less than 1 second.

•The second comparison assembly (1 part, 1 drawing) in its own local directory folder (2 total files) took less than 1 second.

•The third comparison assembly (18 parts, 1 assembly, 12 drawings) in its own local directory folder (31 total files) took less than 5 seconds.

•The fourth comparison assembly (43 parts, 3 assemblies, 23 drawings) in its own local directory folder (69 total files) took less than 12 seconds.

 

Small LAN Temporary Directory:

•The first comparison assembly (1 part, 1 drawing in temp directory) in its own network directory folder (2 total files) took less than 2 seconds.

•The second comparison assembly (1 part, 1 drawing in temp directory) in its own network directory folder (2 total files) took less than 2 seconds.

•The third comparison assembly (18 parts, 1 assembly, 12 drawings in temp directory) in its own network directory folder (31 total files) took less than 6 seconds.

•The fourth comparison assembly (43 parts, 3 assemblies, 23 drawings in temp directory) in its own network directory folder (69 total files) took less than 14 seconds.

 

Large Local Temporary Directory:

•The first comparison assembly (1 part, 1 drawing) in a temp local cpy of the 2400+ file directory took less than 17 seconds.

•The second comparison assembly (1 part, 1 drawing) in a temp local copy of the 2400+ file directory took less than 17 seconds.

•The third comparison assembly (18 parts, 1 assembly, 12 drawings in temp directory) in a temp local copy of the 2400+ file directory took less than 20 seconds.

•The fourth comparison assembly (43 parts, 3 assemblies, 23 drawings) in a temp local copy of the 2400+ file directory took less than 30 seconds.

 

The SolidWorks Explorer "Search Folders" (Options → Search Tab → Search Folders) options are:

     C:\ProgramFiles(x86)\Microsoft Office\root\Office16\Visio Content\

     C:\ProgramData\Microsoft\Windows\StartMenu\

     C:\solidworks data\

     C:\Users\

 

Is there any way to reduce the amount of time necessary to Pack and Go files from relatively large directories of SW files? Or does the user or SW management system (PDM or manual) have to limit the directory folder size to solve this issue? Is this even a directory size/number of contained files problem?

 

[Edit note: "Large Local Temporary Directory" results not originally posted. Added for additional perspective.]

Outcomes