From my observations, utilizing tools I use to monitor system and application performance while testing software applications, several issues exist which cause FTM to have slow performance even on newer high-powered PCs.
First, FTM is a 32-bit application. So it doesn't matter whether you have it installed on a 32-bit OS or a 64-bit OS. And you could have all the RAM installed that your motherboard is capable of addressing and that still wouldn't help with FTM's performance. A 32-bit Windows application will only address up to 2GB of memory unless coding within the application specifically tells it to be "large address aware". Even then it will only address up to 4GB of memory. A 64-bit application could be able to address more RAM than current PC motherboards will even hold. Boggled up in this is that FTM uses .NET, which has its own limits towards memory addressing.
Second, the FTM application does not take advantage of the processing capabilities of multi-core processors. So, even on my PC with a 6-core processor, FTM only uses the capabilities equivalent to a single core and the FTM application will bog down when it hits between 16-17% of the total CPU capabilities (100% / 6-cores = 16.66~% per core).
I have researched the specifications for the underlying database engine used for FTM development and the engine itself is 64-bit capable. So there is no reason I see for a 64-bit version of FTM not being released yet other than they just haven't developed and released one. Even with the existing 32-bit application there is no reason I see why it hasn't been coded to detect and take advantage of full system capabilities other than they just haven't coded it to do so. All we can do as FTM users is keep complaining to them for better performance.
Mary
First, FTM is a 32-bit application. So it doesn't matter whether you have it installed on a 32-bit OS or a 64-bit OS. And you could have all the RAM installed that your motherboard is capable of addressing and that still wouldn't help with FTM's performance. A 32-bit Windows application will only address up to 2GB of memory unless coding within the application specifically tells it to be "large address aware". Even then it will only address up to 4GB of memory. A 64-bit application could be able to address more RAM than current PC motherboards will even hold. Boggled up in this is that FTM uses .NET, which has its own limits towards memory addressing.
Second, the FTM application does not take advantage of the processing capabilities of multi-core processors. So, even on my PC with a 6-core processor, FTM only uses the capabilities equivalent to a single core and the FTM application will bog down when it hits between 16-17% of the total CPU capabilities (100% / 6-cores = 16.66~% per core).
I have researched the specifications for the underlying database engine used for FTM development and the engine itself is 64-bit capable. So there is no reason I see for a 64-bit version of FTM not being released yet other than they just haven't developed and released one. Even with the existing 32-bit application there is no reason I see why it hasn't been coded to detect and take advantage of full system capabilities other than they just haven't coded it to do so. All we can do as FTM users is keep complaining to them for better performance.
Mary