I've tested all of this pretty thoroughly. The "theoretical" memory access limit of the 32 bit universe is 4 gig.
32 bit ProE on 32 bit Windows - ~2.75gig (with 3g switch enabled)
32 bit ProE on 64 bit Windows - 4 gig
64 bit ProE (requires 64 bit OS) - somewhere in the exabytes
So is it safe to conclude that 32-bit Pro-E performs better on 64-bit OS
Our reason for not using 64 bit Pro/E is the error messages we encounter in embedded and stand alonebrowsers. Pro/e itself had no issues. But windchill users were getting compatibility error messages all the time.
Yugedra Bhide
Norse Dairy Systems
In Reply to John Crockett:
I've tested all of this pretty thoroughly. The "theoretical" memory access limit of the 32 bit universe is 4 gig.
32 bit ProE on 32 bit Windows - ~2.75gig (with 3g switch enabled)
32 bit ProE on 64 bit Windows - 4 gig
64 bit ProE (requires 64 bit OS) - somewhere in the exabytes
32 bit ProE on a 64 bit OS isn't any faster, but somewhat larger memory models don't crash. For those modelsdancing near the 2.75 gig memory limit, that extra memory headroom can be a huge improvement. As you share models with other folks running 64 bit (who don't have your memeory constraints) you will increasingly run into situations where you can't even open the master reps of their assemblies.
64 bit ProE:
Everyday tasks run 5-10% faster, for no reason that I can explain, but it is true.
Virtually unlimited memory capacity
Random "Matrix our of bounds" errors (which crash the ProE session) almost never happen
Models are 100% backwards compatible, except for the ability to exceed memory limits of 32 bit, but simplified reps can be used to workaround that issue... but that does not help for drawing files.