Continue to Site

Welcome to MCAD Central

Join our MCAD Central community forums, the largest resource for MCAD (Mechanical Computer-Aided Design) professionals, including files, forums, jobs, articles, calendar, and more.

dual processor or ram for upgrade

jphillips42

New member
I have an option of doubling my ram to 4 gig or adding a 2nd processor to my machine for an upgrade. Which would have the biggest impact on the regen times in pro wildfire 2?
 
You can also look at the maximum Ram you usualy use with task manager.


If you never reach the 2GB you have, adding Ram will not have any effect.


(Do you know that you must use 64bits OS for using 4GB ?)


The best thing for reducing regen time would be to change your processor for an higher speed, I think.
 
gbon said:
You can also look at the maximum Ram you usualy use with task manager.


If you never reach the 2GB you have, adding Ram will not have any effect.


(Do you know that you must use 64bits OS for using 4GB ?)


The best thing for reducing regen time would be to change your processor for an higher speed, I think.


4 GB is usable in 32-bits Windows, with the appropriate settings. Giving 1.1 GB to Windows and 2.9 for programs (userva=2900) seems to be a safe setting for most.


You're correct for all other items.
 
The second processor won't speed up Pro but if you run a lot of applications simultaneously it will speed up the GUI and task switching. It is particularly good if you run analysis solver in the background.

I think at WF3 Pro is supposed to start being a little more multi threaded?
 
if you have WF on a desktop along with email , word etc. then you can use 3gb per process.


so 3gb for xtop.exe which leaves 1 gb for OS and office apps etc.


dual processors are good for guys with mechanica or as previously mentioned, if it is used as a desktop pc and not standalone cad only. also moving on as previosuly said with WF3...
 
Some people report that leaving 1GB for Win can be too little and add the "/userva=2900" switch to raise kernel memory to 1196 MB.


Setting 3 GB for 'xtop' does not mean other programs live in the remaining memory space. It merely allows EVERY program to allocate this amount of memory, which otherwise would be "restricted" (if you consider this a restriction) to 2 GB. So having all kinds of programs open will eat away memory space and cause swapping to virtual (harddisk) memory.
 
We are using 32bit Dell 670 with 4 GB RAM and we do settings as below to help XTOP to handle more than 2 GB RAM


c:\Apps\proe\i486_nt\obj\imagecfg.exe -l xtop.exe


Note:Close XTOP before doing this.


And also we enabled 2+2 processors
 
And also I am usingbelow switch


I am not sure this is usefuly


[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /PAE /3GB /NoExecute=OptIn
 
Yes that is needed to for Pro/E to access more than 2GB of memory BUT you are now at risk of having the OS run out of memory. Try this switch: /userva=2900. This will allocate 2.9Gb to application address space and leave 1.1GB to the OS. This has been documented on this board, at PTC's web site and Microsoft's.
 
I am currently having problems with slow response time with ProE. Even on smaller models with no regeneration going on. It seems that making selections, panning, rotating, zooming (no matter what environment I am in...shaded, wireframe, etc...) takes a while for my system to respond. This is all on a new system.


Hereis my system configuration:


Windows XP on a Dell Optiplex GX745


Pentium D CPU 3.40 GHz (Dual)


2 GB RAM


2007-04-11_153242_system.zip


Any help would be greatly appreciated.
 
Or a video card that is either misconfigured, has wrong drivers or is not good.


Another timewaster is search paths. But this only comes in action when retrieving. When files are not found and search paths refer to network drives (lots of paths and parts) then you can be waiting forever.


Alex
 
I previously had a system that had a 128 MB ATI Radeon X600 SE graphics card and wasn't seeing this problem. Also, we are running 2 other systems with this same graphics card and those aren't seeing this problem. Is it possible that there's a problem with my processor or if it is just my graphics card itself, how do I test it/them?
 

Sponsor

Articles From 3DCAD World

Back
Top