64-bit over 32-bit

[MDGroup]

Co-Worker has a computer that can run Windows 64-bit, but they only installed the 32-bit operating system. So, SW is also running as 32-bit.

If the computer is switched to 64-bit (and SW is re-installed as 64-bit), what will the improvements be? Is it going to be significantly faster? Better stability (less crashes)

IT guy says that it wont improve performance, and could cause issues with drivers. He doesn't want to spend his time making the upgrade.

Any thoughts? Will there be a noticeable improvement running SW on 64-bit over 32-bit?

Thanks

 

[CorBlimeyLimey]

A 64 bit system will not be faster. It will allow more RAM to be used, which in turn might make the system more stable ... especially if dealing with large assys.

 

[gwubs]

CBL and your IT guy are correct. No speed gain, and we do have driver issues. Not insurmountable, but definately a thing to consider. If you need the RAM, and many of us do, you want to go 64bit. If you don't need the RAM (more than 3GB) run 32 bit.
Gerald

 

[MDGroup]

So, the general consensus is that there really wont be a significant (if any) improvement to switch to 64-bit, so we should probably just leave it at 32-bit.

Thanks for the input.

 

[CorBlimeyLimey]

If the assys are large, or the parts have lots of features (especially complex ones), a 64 bit system will be a definite benefit.

If your current crashes are not caused by lack of RAM or system resources, then you probably don't need a 64 bit system. 64 bit is no more stable than 32 bit, it just allows you to work with larger assys/parts.

 

[321GO]

-CorBlimeyLimey

assemblies larger than 3GB!, do they even exist?

To me, the memory expansion over 3GB is only neccesary when doing fea or cfd.

 

[ctopher]

I experience 64 to handle surfacing better than 32.

Chris
SolidWorks 10 SP4.0
ctopher's home
SolidWorks Legion

 

[CorBlimeyLimey]

"assemblies larger than 3GB!, do they even exist?"
Although I have never come even close to a 3GB assy, I would be surprised if they didn't exist. Some users work with massive assys.

Also, an assy doesn't have to be anywhere near as big as 3GB, for the system to use over 3GB of memory (physical and virtual). It's not only FEA and CFD which require large amounts of memory.

 

[DesignerGuy16]

I can get SW to crash at will if I want to with 32-bit because of the memory. Due to complex features, and very large machine assemblies.

It all depends what you're doing. If you don't get to very complex free-form surfaces/helix shapes and enormous assemblies you probably won't see much gain.

If you do, and if you also do any FEA analysis, you will see improvements in speed overall. These are the major areas that start to eat memory.

James Spisich
Design Engineer, CSWP