Graphics Cards

[jlbmech]

I realize I have had allot of questions today, but I am a new user so please forgive.

This question however involves the computer that you are running Solid Edge on. At the company that I work for we create skids that are approximately 10 ft X 13 ft X 8 ft tall, with large components on the skids and lots of pipe connecting them.

The computers run extremely slow (I can't stress this enough) once the assy gets very involved.

We are running Pentium 4 (3.2G), Windows XP Pro SP2, 2G RAM, and a Quadro FX 550 video card (128M RAM).

Is my computer inadequte for this type of modeling and if not is this slow normal. If not how to speed it up; and I am currently using simplified parts.

 

[swertel]

The size of your assembly is not outrageous for Solid Edge or your workstation setup.

There are several things we need to do to find the bottleneck in your system. Right off hand, I'm guessing it's your network.

1) Open the task manager, all the apps you normally have running, and SE with the largest assembly open. Does the peak memory comit charge exceed the amount of installed RAM? If so, install up to 4GB RAM.

2) Is you page file set to a static size and not to a variable size controlled by Windows? Make sure the page file is set to approximately 2X your RAM (4048-4048). It is more efficient to locate the page file on a second hard drive with its own controller other than the one Windows and your applications is installed on.

3) What is slow, specifically? Rotating your model? Updating a part from a feature change? Adding components to the assembly?

4) Are your files stored on the network or locally?

5) Are you running Insight or TeamCenter?

--Scott

--Scott

http://wertel.eng.pro

 

[jlbmech]

SWERTEL

1.) It says my peak is approx. 722,000, but I am not computer savy enough to know what that means.

2.) Again with the savy.

3.) Rotating gets choppy, XpresRoute takes literally minutes to generate a piece of pipe, and adding components takes about the same amount of time.

4.) All of our files are stored on a local network.

5.) I am not running Insight or TeamCenter.

 

[Schipperus]

Welcome new user!!!

Check the network performance...

Again open task manager, view the network performance tab. Now open a large assembly, maybe do some XpressRoute stuff.. The graphics show how much of the network capacity is used.

Also, if the graph jumps up and down, there might be a switch problem. just had this kind of problem a few weeks ago.

Then, for relaxed working. Make sure all parts you don't need are inactivated, or even hidden and unloaded. For just viewing large assemblies make a simplifies assembly, or hide all non-visible parts and unload them.

Greets, IJsbrand

 

[swertel]

2)
Right Click on My Computer and select Properties.
Click on the advanced tab.
In the Virtual Memory group, click the Change button.
Set the Custom Value to min=4048 and max=4048 and click Set.

If you have a second hard drive, you should set the page file on the second hard drive and not the drive where the OS is installed.

---
Do you have anything running in the background? Outlook? Or an animated GIF on your desktop? Weatherbug? Or similar system tray tool? Try running SE with those items disabled.

What type of Antivirus product do you use? Do you have permission to set the A/V to exclude SE files? If so, do so. (.par, .asm, .psm, .dft, and .pwd)


--Scott

http://wertel.eng.pro

 

[onefjef]

jlbmech,

My machine at work is similar in setup. In SE a simple thing to try is to turn off the Drop Shadow feature. This is a button located on the Main toolbar. Looks like a box with a shadow behind. The drop shadow consumes system resources that are better used elsewhere.

Another thing. If your Windows is set up to use many "effects" like menu fading then you should consider turning them off. Right click on My Computer on the desktop, select the Advanced tab, select the radio button labeled "Adjust for best performance".

Jef

 

[KENAT]

I think the above posts have covered most things but also shaded no hidden edges uses the least processing. (Bad thing is you can't always see what you're doing)