Brian Hamilton Our app handles healthcare services delivery (clinical, scheduling, billing) - about 1,500,000 lines of Delphi code across serveral modules (Case workflow/workload, web Portal, EDI out/in, data exchange, graphic Kbase)
Martyn Spencer Thank you. I was able to find a source for the software we bought in 1999 (a calendar build facility)
No performance penalty in such case. Delphi native Win64 apps are likely to be slower than Win32 even on a 64-bit Windows, due to bigger pointer size, and less optimized code in the Delphi RTL. 64-bit is IMHO required only if you need to consume a lot of RAM (more than 2/3GB).
Karl Walter Keirstead You should be fine with 32-bit Delphi unless as noted that your appication uses more memory but there is a twiddle bit in the .exe header that will give you more allocation.
If the data addresses are aligned properly, there is no 64-bit pointer penality over 32-bit programs unlike what people might say running under WOW because on an x86-64 machine, 32-bit pointers dont exist and are merely emulated by WOW as 64-bit.
Said another way, a 32-bit windows program actually runs in a 64-bit address space and WOW generates that 64-bit address space.
So you your 32-bit program will run closely as well to a natively produced 64-bit binary as long as there is proper alignment.
I will add that WOW imposes a 32-bit boundary restriction because the emulated machine registers, well, cant address beyond it.
Jennifer Powell problems with pointer size is about the used memory to store them e.g. as reference to objects or string. TMyObject.InstanceSize will be bigger on win64. This is a real speed penalty on some cases since it will consume more ram andcpu cache. Wow64 has no effect on that.
Hello and welcome.
ReplyDeletewhat does the app do? (video processing, or?)
ReplyDeleteBrian Hamilton Our app handles healthcare services delivery (clinical, scheduling, billing) - about 1,500,000 lines of Delphi code across serveral modules (Case workflow/workload, web Portal, EDI out/in, data exchange, graphic Kbase)
ReplyDeleteMartyn Spencer Thank you. I was able to find a source for the software we bought in 1999 (a calendar build facility)
No performance penalty in such case. Delphi native Win64 apps are likely to be slower than Win32 even on a 64-bit Windows, due to bigger pointer size, and less optimized code in the Delphi RTL. 64-bit is IMHO required only if you need to consume a lot of RAM (more than 2/3GB).
ReplyDeleteKarl Walter Keirstead You should be fine with 32-bit Delphi unless as noted that your appication uses more memory but there is a twiddle bit in the .exe header that will give you more allocation.
ReplyDeleteIf the data addresses are aligned properly, there is no 64-bit pointer penality over 32-bit programs unlike what people might say running under WOW because on an x86-64 machine, 32-bit pointers dont exist and are merely emulated by WOW as 64-bit.
Said another way, a 32-bit windows program actually runs in a 64-bit address space and WOW generates that 64-bit address space.
So you your 32-bit program will run closely as well to a natively produced 64-bit binary as long as there is proper alignment.
I will add that WOW imposes a 32-bit boundary restriction because the emulated machine registers, well, cant address beyond it.
Jennifer Powell problems with pointer size is about the used memory to store them e.g. as reference to objects or string. TMyObject.InstanceSize will be bigger on win64. This is a real speed penalty on some cases since it will consume more ram andcpu cache. Wow64 has no effect on that.
ReplyDelete