Did this article resolve your question/issue?



What are the advantages of the 64-bit version of OpenEdge versus the 32-bit version


TitleWhat are the advantages of the 64-bit version of OpenEdge versus the 32-bit version
URL NameP111328
Article Number000142353
EnvironmentOpenEdge 10.X
OpenEdge 11.X
All Supported Operating Systems
Question/Problem Description
What are the advantages of the 64-bit version of OpenEdge versus the 32-bit version
Can I get a better performance by changing from 32-bit to 64-bits
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
The advantages revolve around the increase in address space, and the ability to address more than 2Gb of RAM.

Thanks to this, it's possible to allocate more then 2Gb of memory for the database buffer pool, which allows for better scale-ability for larger, multi-gigabyte databases.
Current versions of OpenEdge (as of November 2005) can address up to 116Gb of RAM of memory; this limit might be further lifted in future releases.

Performance on a 64-bit platform can vary very much depending on your specific application, when compared to the 32-bit of OpenEdge for the same platform.
The product is being tuned continuously to achieve better and better performance with 64-bit architectures.

With OpenEdge 10.1A, 64-bit .r code has been introduced; while this introduces some problems if you plan to deploy on both 32- and 64-bit platforms, the performance advantage introduced by this feature is substantial (around 15% according to some benchmarks, but of course your mileage may vary).

The compatibility issue with .r code mentioned above has been fixed and is no longer an issue in OpenEdge 11.

On the downside, the 64-bit version of OpenEdge will have a larger memory footprint, both because the executables are bigger, and because the in-memory structures need to allocate 8 bytes for each pointer, rather than the 4 bytes necessary in the 32-bit version.
References to Other Documentation:
Progress Article:
 OpenEdge 10.x and 11.x R-CODE bit compatibility rules
Last Modified Date11/20/2020 7:23 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.