Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- From: TOP <kellnerp@xxxxxxx>
- Date: Thu, 07 Jun 2007 07:44:22 -0700
Dale,
This one was complex so I would not make a generalization. Patterns
will of course slow an assembly just like anything else. And with
patterns there is the danger of making a mate to a patterned item
which will cause a bigger hit. Ditto with in-context to a patterned
item. For that reason when I mate, I do it rolled back to the mate
tree. Then doing no-no's is less likely.
I will also dissolve patterns if and when they are causing a problem
with performance and it can be done without causing other problems. I
place the dissolved components in a folder so I can delete and
recreate it as necessary.
BUT, the problem I had was with saving; it was orders of magnitude
slower than it should have been, and it could have been patterns, in-
context or a combination of them peculiar to this file. Ordinarily
patterns don't cause the kind of major problem I was seeing.
TOP
Since the pattern now exists in a subassembly, can we conclude that there
was a problem with that particular pattern, instead of component patterns
in general? I don't want to hear later of CAD admins banning component
patterns.
.
- Follow-Ups:
- Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- From: matt
- Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- References:
- ASSEMBLY PERFORMANCE: Poisoned Assembly
- From: TOP
- Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- From: TOP
- Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- From: Wayne Tiffany
- Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- From: TOP
- Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- From: Dale Dunn
- ASSEMBLY PERFORMANCE: Poisoned Assembly
- Prev by Date: Re: Has any one tried a 7600 GS graphic card?
- Next by Date: Re: Macro - last user retains control
- Previous by thread: Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- Next by thread: Re: ASSEMBLY PERFORMANCE: Poisoned Assembly
- Index(es):
Relevant Pages
|
Loading