32-bit vs 64-bit

[vandewinckel]

Hello


We're purchasing new workstations. Is anyone using Wildfire 3.0 on a 64-bit system. Is there a difference between 32-bit and a64-bit system.


Thanks

 

[looslib]

The biggest reason to go with 64-bit OS and applications is if you are running out of memory with Wildfire on a 32-bit system.

 

[jridge]

I have used Wildfire 3.0 on a 64 bit system. As looslib states, there is the advantage of gaining addressable memory, since the 32 bit systems are typically limited to the first two GB of memory. There is a program that extends the 32 it addressable size to 3GB, but not without penalty. In some cases the "3 GB switch" causes issues.

We purchased 2- 64 bit single processor systems with 8 GB of memory and 1 dual processor with 16 GB. The difference really stands out when performing analysis with programs like Mechanica or AnSys. Our in house benchmarking placed the 64 bit machines at nearly twice the speed of our 32 bit machines in completing large element count static, dynamic, contact and modal analyses.

For WF3, the real beauty is being able to easily load large assemblies with no performance reduction. We were able to load a large assembly and use other programs like Excel, Convert, Internet Explorer and windows explorer simultaneously with no degradation in performance. Interestingly enough, the dual processor 64 bit system revealed only marginal gains in performance over the single processor 64 bit systems.

If anything, the video card in these systems is the bottleneck, so a recommendation, if you are thinking of going 64 bit, is to go with the single processor and spend the money on the best video card available.

 

[vandewinckel]

Thanks for the info. It was very helpful.

 

[SW]

Is there any disadvantage to running the 64 bit version? I've ordered a new laptop and could install the 64 bit version of XP and Wildfire 3.0. Is there any reason not to do this?

Sam

 

[looslib]

A lot depends on what other applications you need to run on the laptop. Not everything has 64bit code available.

 

[canopys]

I have a 64 bits laptop (precision M64) with XP 64 dans WF3. I had no issues with it only a snag with mousse drivers but I found themon intenet.


The best will be to investigate if all the softs you need are aivailable in 64 bits.

 

[shipley00]

I have used Wildfire 3.0 on a 64 bit system. As looslib states, there is the advantage of gaining addressable memory, since the 32 bit systems are typically limited to the first two GB of memory. There is a program that extends the 32 it addressable size to 3GB, but not without penalty. In some cases the "3 GB switch" causes issues.

We purchased 2- 64 bit single processor systems with 8 GB of memory and 1 dual processor with 16 GB. The difference really stands out when performing analysis with programs like Mechanica or AnSys. Our in house benchmarking placed the 64 bit machines at nearly twice the speed of our 32 bit machines in completing large element count static, dynamic, contact and modal analyses.

For WF3, the real beauty is being able to easily load large assemblies with no performance reduction. We were able to load a large assembly and use other programs like Excel, Convert, Internet Explorer and windows explorer simultaneously with no degradation in performance. Interestingly enough, the dual processor 64 bit system revealed only marginal gains in performance over the single processor 64 bit systems.

If anything, the video card in these systems is the bottleneck, so a recommendation, if you are thinking of going 64 bit, is to go with the single processor and spend the money on the best video card available.

I'm curious to know which video cards you are running that's giving you a bottleneck? From everything I've read, video cards are the bottleneck for things that render including Mechanica and Large drawings, but not so much for parts and assemblies.