SW2006 crawling on large assemblies

Did you try to open the assembly (part) first before opening the drawing? This was an issue with older SP's of 2006 Wim

Yes, everything is local...I spent most of yesterday running the 'Conversion Wizard' on a bunch of older files because I've heard "unconverted" files can clog things up...CW is a slow too, sometimes it'll take 20 minutes doing one file. The files appear to be about the same size as the originals...even tried SaveAs on a couple large ones once they opened.... still too forever.

Seems to affect any large ~20-30Mb files

Thanks

I'll check out eco-squeeze...

Jeff Mirisola wrote:

Yes, the assemblies open "reasonably" quick, I can find no problems with them once opened, everything points to the correct file and there are no assy errors (that I can see) With the assy open, the drawings still take a very long time (15-20 minutes sometimes)

Shouldn't the CPU be churning away when opening these things?...mine sits near zero most of the time this happens...

I'm going to try SP5 when I get to work today...

Thanks

Wim wrote:

"WC" a écrit dans le message de news: H_l2h.2929$ snipped-for-privacy@tornado.texas.rr.com...

I've had that kind of pb, and cleaning out the temp folder solved it.

Huh...that's strange. What are your system specs?

quoted text -

It's a 2 year old Xi...148 Opteron FX51, 2Gb ram, Fx1100, 80 Gb SATA (about 2/3 full) XP Pro.. it was a smoking machine.

This AM SW was so flaky most of the toolbar buttons were staying "pressed" I decided to do another clean sweep of the Reg and removed all traces of SW(bs)...I guess it's all part of "system maintenance" ...hmmm

Jeff Mirisola wrote:

Show quoted text -

decided to do another

part of "system

Show quoted text -- Hide quoted text -- Show quoted text -

Same ol' s&!%... full wipe of swx made almost no difference, opened the assy OK been waiting about 15 minutes for the drawing to open...

CPU idle, SW Mem Usage ~200Mb

I'm stumped, and basically dead in the water awaiting a call back from the VAR...

...hmm

WC wrote:

decided to do another

part of "system

Hi, I've had a similar problem it occurred with large assemblies and drawings, Firstly with the ssemblies once copied using explorer open them up and resolve so that the new parts are showing check part and sub assembly file paths.

With drawings, what occurred with mine was pretty nasty, i had BOM templates and drawing templates in local folders , the new copied drawing files didn't recognize them and I had to open everything in Rx mode and then rebuild my drawings.

WC wrote:

OK been waiting about 15

decided to do another

part of "system

I commiserate with you on the slow down. However, from what you say the action of copying with SWExplorer brought this on. So it may be time to investigate where SW thinks it is getting files from. From what I can see in 2006, if a drawing was made in one directory structure and is asked to load from the same assembly moved to another file structure it can get very slow. Once you get the drawing open, look at the File/Find Reference and see where the drawing thinks it is getting it's information. If the drawing has to go through the whole recursive file search for each part and assembly this can take a long time. Do you have your References path set in a way that SW can easily search for new files? Is Search External references checked in Tools/Options? Just some thoughts. Hope it helps.

Thanks for the input...

This is actually about the 5th generation of this assembly, originally done in SW2001... We use 'project folders' for the related parts/aasy, with more folders for purchased items, these purchased items reside in their own Vendor specific folders, ie McMaster, Parker, Hub City, etc.

As time goes by what started in 001, went to 002, then 003, then 004, etc. As the assembly evolved it would pull from all the previous project/reference folders, plus a few more. I just checked a copy of the 'Find References' output from the assy causing trouble, it's pulling from ~35 folders.

I'm thinking there is a bad part/sketch reference buried somewhere deep, but the drawing/assembly opened 'normally' here at home (FX64, 1Gb ram, cheapo video card), so that seems to point to a windows/work computer problem

I noticed the CPU was actually doing something at home (~40% ~70%) while opening the files (with the same file structure) while at work the CPU is usually idle doing the same thing, Not Responding, I usually kill it after 10 minutes of 'trying' to open.

Talked to the VAR yesterday, they're going to SW for input, I'll keep plugging away and probably be doing some work from home this weekend... hmmm.

Thanks again

T> I commiserate with you on the slow down. However, from what you say the

Did you check to see whether the list of paths in the assembly and drawing agreed?

list of other stuff to look for that kills assembly performance:

- more than minor in context work

- mating to history dependent assembly items such as in-context, assembly features, assembly sketches reliant on part geometry, Hole Series, component patterns, reference geometry in the assembly created from part locations or other in-context items, smart fasteners

- verification on rebuild

- perpetual rebuild symbols in the tree

- feature or mate errors (if warnings are set to never be shown, you may have problems you don't even know about)

- out-of-context relations or multi-context

- there might be settings at home that are avoiding the problem such as view only, lightweight

No, I'll check that this evening, or this weekend...

Thanks fo rthe input

WC

T> Did you check to see whether the list of paths in the assembly and > drawing agreed?

Sorry for the delay, took most of the day for the message appear here at work...

I'll dig into this more this weekend...

Thanks a bunch for the leads

matt wrote:

Hi,

I am hear> Sorry for the delay, took most of the day for the message appear here at > work...