What OpenEdge Native support for Microsoft Windows64?
OpenEdge 10.2A was the first 64-bit version of OpenEdge certified for the 64-bit Operating System versions of Windows. However, support for WIN64 was not included in the intial release of OpenEdge 10.2A.
On April 9th, 2009 the OpenEdge 10.2A01 Service Pack for Win64 was made available on the ESD site. This is the Service Pack which fixed the various performance issues related to the delay of the OpenEdge 10.2A 64-bit release on Windows 64-bit.
On September 2nd, 2009 the OpenEdge 10.2A02 Service Pack for Win-64 was made available on the ESD site.
On March 10, 2010 the OpenEdge 10.2A03 Service Pack for Win64 was made available on the ESD site. This is the last service pack for OpenEdge 10.2A.
OpenEdge 10.2B and above are available for Windows 64-bit without availability restrictions. OpenEdge 11.3 includes a full GUI client.
For the latest Windows 64-bit supported platforms, please reference Solution "Which versions of OpenEdge have a 64-bit edition?" and the Platform and Product Availability Guide and Reference.
This release is a "Server Only" win64 implementation which provides access to more than 2 Gigabytes of memory for OpenEdge servers:
- OpenEdge RDBMS
- DataServer
- Webspeed
- AppServer
- OE Development Server (for Character and batch clients)
The Server edition also includes the .NET OpenClient interface DLL's as native 64-bit programs, enabling the use of the Open Client interface to develop 64-bit applications.
OpenEdge 64-bit releases for Windows through release 11.2 do not include Win64 GUI client support. Customers wishing to use this server-only product with a GUI client would need to connect to the database or AppServer/WebSpeed via a remote machine. However, character development activity can be performed using the 64-bit Character Client with the OE Development server license. OpenEdge 11.3 includes a full 64-bit GUI client.
What are the benefits of Win64?
The OpenEdge Windows 64-bit product allows more shared-memory to be allocated to the database buffer pool, which dramatically improves the performance of applications that have a low in-memory buffer hit rate or that are disk bound.
Is there any limitation with Win64?
Please note that under certain circumstances, you may not achieve the operating performance on Win64 that you may have expected. This may be noticed during CPU-intensive application operation. Progress has worked very closely with Microsoft and Intel to determine the source of the performance issue. It has been determined that this issue could arise during CPU intensive operations for Windows applications running on modern machines (post 2006) with newer CPUs. In particular, it appears that the issue may be isolated to the Intel EM64T chip.
If your application is CPU intensive and if you plan to operate on Win64, you may experience improved performance using systems with the AMD 64-bit series of chips due to the larger L1 Data Cache associated with these chips. OpenEdge will operate without error on systems using the Intel EM64T chips, however, our benchmarking has shown that you may experience a performance degradation with CPU intensive applications as compared to running on systems with the AMD 64-bit chips.
As with the introduction of any new operating system, you should plan to carry out performance testing of your application before you release into a production environment.
