Piping assemblies running slow

Discussion created by Guest on Sep 25, 2005

Like • Show 0 Likes0
Comment • 5

I asked around regarding the eDrawings issue. There is an option to save the eDrawing for all configs. I wouldn't have expected this to include all configs for parts in the assembly but if it does that would explain it. Can you check the file size with this option set to the current active config only.

Development Manager - Routed systems.

Outcomes

5 Replies

Guest Sep 25, 2005 1:47 AM
Hi Merry

Yes, adding large numbers of configurations to the library models will cause some performance degradation but I wouldn't expect it to to be as bad as you suggest. I am very surprised that it also affects the eDrawing.

I would be happy to investigate this if you could send me some data though I understand it may be inconvenient for you to do so.

Let me know if you are happy to send the data and I'll mail you the address, It'll be too large to send by email.

Cheers

on 2005 24 22:47 Merry wrote:
> We do a number of quite large piping installations and I have noticed that it
> really bogs down the computer. I was wondering if it may be because of the
> large number of configurations that I have in most of my library parts (e.g. the
> RFWN flange has over 900 configurations).
>
> I noticed this on a relatively small assembly when I made a model of an 'all
> thread bar'and after adding all of the diferent thread sizes and a heap of
> lengths for each size (I went up in 5mm increments) this ended up with over 2000
> configurations. I used 4 of these parts in the assembly and it bogged right
> down. Even creating an eAssembly ended being a 12MB monster that needed 1.3 GB
> of RAM to open.
>
> Has anybody else come to this conclusion?
Development Manager - Routed systems.
EditDeleteLike • Show 0 Likes0
Actions
Guest Sep 25, 2005 1:47 AM
We do a number of quite large piping installations and I have noticed that it really bogs down the computer. I was wondering if it may be because of the large number of configurations that I have in most of my library parts (e.g. the RFWN flange has over 900 configurations).

I noticed this on a relatively small assembly when I made a model of an 'all thread bar'and after adding all of the diferent thread sizes and a heap of lengths for each size (I went up in 5mm increments) this ended up with over 2000 configurations. I used 4 of these parts in the assembly and it bogged right down. Even creating an eAssembly ended being a 12MB monster that needed 1.3 GB of RAM to open.

Has anybody else come to this conclusion?
EditDeleteLike • Show 0 Likes0
Actions
Guest Sep 25, 2005 1:47 AM
Sorry for my lack of responce - got a bit busy. I have several configs of the model, but I only saved the one config with eDrawings.

I have just re-created my all-thread as a part template (i.e it only has the various diameters, but the length will become unique to each project it is used in). I will replace my previous library parts with this version and see if it reduces the time & file size. I will let you know the results.
EditDeleteLike • Show 0 Likes0
Actions
Guest Sep 25, 2005 1:47 AM
on 2006 7 07:25 Gary Strobel wrote:
> Interesting.
> I have noted that threaded pipe routes are much slower (significantly so) and now
> think it is because of the part file size of each configuration. The route assembly
> files are considerably larger than similar routes with pipes. Perhaps the same case
> of making a subset of the file with only the required configuration should be applied
> to threaded routes as happens with pipe routes?

Yes, I would say so. You should always avoid carrying around data you will never use. But as always, take a safe copy of the files first, just in case.

Development Manager - Routed systems.
EditDeleteLike • Show 0 Likes0
Actions
Guest Sep 25, 2005 1:47 AM
Interesting.
I have noted that threaded pipe routes are much slower (significantly so) and now think it is because of the part file size of each configuration. The route assembly files are considerably larger than similar routes with pipes. Perhaps the same case of making a subset of the file with only the required configuration should be applied to threaded routes as happens with pipe routes?
EditDeleteLike • Show 0 Likes0
Actions

Piping assemblies running slow

Outcomes

Related Content

Recommended Content