Pro/E stirbt bei 1,6 GB Speichernutzung / Pro ENGINEER
By colonel 22. Februar 2001, 13:41

Hallo Leute,

wir haben hier ein Riesenproblem mit Pro/E. Pro/e stirbt bei einer Speichernutzung von 1,6 GB. Laut Rand- und PTC-Hotline ist dieses Problem bekannt. Die Empfehlungen zur Abhilfe waren aber mehr als lächerlich.

Wer hat ähnliche Probleme ?

By soave 22. Februar 2001, 17:10

Wir hatten ähnliche Probleme und haben durch Vereinfachungstechniken die Datenmenge reduzieren können.
Das Problem liegt an Windows NT(32bit-Betriebssystem).
Vielleicht hilft der "Lösungsvorschlag" von PTC wahrscheinlich ist der dir auch schon bekannt)
set in control panel: system - performance: the virtual memory to all maximum size set to 2Gbytes which is the theoretical limit for memory addressing for executables compiled in 32 bits. The actual limit of Windows NT is around 1.6 Gbytes

By colonel 23. Februar 2001, 07:27

Ja diese Antwort kenne ich. Typisch für PRO/E. Wenn PRO/E nicht läuft ist das Betriebssystem, die Hardware oder das Wetter schuld. Komisch nur, dass andere CAD-Systeme, die mit dem gleichen Betriebssystem arbeiten diese Grenze nicht haben. Siehe UG.

By eis 23. Februar 2001, 09:17

Es gibt Neuigkeiten zu diesem Thema bei PTC ( verfolge den SPR 848636 schon länger ) :

Description
-----------------
Pro/ENGINEER exits when running out of memory on a Windows NT workstation prior to reaching the 2 GB memory limit for 32 Bit applications on this OS.

Background
-----------------
Currently Pro/ENGINEER running on Windows NT workstations is a "32-bit" process running on a "32-bit" Operating system. The operating system and the compiler used to create the executable cause Pro/ENGINEER to be constrained by the "32-bit limitation".

With respect to Pro/ENGINEER, the "32-bit limitation" refers to the amount of memory that can physically be allocated for a SINGLE process. Memory is allocated to memory addresses, which in the computing world are represented in binary format (one's and zero's). The following are two examples:

0000 0000 0000 0000 0000 0000 0000 0000 a(32 zero's)
0000 0000 0000 0000 0000 0000 0000 0001 a(31 zero's and 1 one)

Each combination of ones and zeros represents a different memory address or pointer. There are approximately 4 Billion combinations or approximately 4 Gigabytes of memory addresses. This value comes from the number of options for each bit and the number of bits available or 2^32 = 4.3 Billion. This limitation is independent of whether the memory is Swap or Ram.
In general this limitation is a hard limitation on 32-bit platforms. However, there are some exceptions.

Alternate Technique
-----------------
The following examples of methods for "Kernel Tweaking" which have been done for different Operating systems to attempt to allow the application to utilize more of the 4GB of addressable memory available and for the OS to use less:

Windows NT Enterprise Server with "4 GB Ram Tuning"
Microsoft has developed a version of Windows NT Server, which will allow applications to allocate approximately 3GB of the available 4GB, leaving 1GB for the OS. In practice this results in Pro/ENGINEER being able to use about 2.4 GB of memory. The details of this configuration are available on the Windows NT Server Enterprise CD. In summary, the boot.ini file needs to be modified to add the "/3gb" switch and the executable itself needs to be modified by utilizing the, "imagecfg.exe" tool which is also available on the Enterprise server CD.

NOTE: This configuration is very difficult to support and resolving SPR's is extremely cumbersome due to the amount of time it typically takes to reproduce an exit when the problem or problems occur when over 2GB of memory have been used.

Sun Solaris 2.6 with a "Kernel Tweak"
Sun's Solaris 2.6 operating system has a similar capability to reduce the amount of addressable memory the OS will receive. Sun's tweak allows approximately 3.75 GB of memory to be accessible by the application. Actual limitations are not available, but again there is "overhead" expected and the actual amount of memory used will more likely be closer to 3.25GB. The link for this configuration can be found at:
http://www.sun.com/technical-computing/ISV/PTCFaq.html#MORETHAN2G


Resolution
-----------------
PTC, in conjuction with Microsoft, has investigated this issue. Due to technical limitations in Windows NT 4.0 and 2000, the available addressable memory for Pro/Engineer on those OS's is 1.7 GB. This limitation has been confirmed by Microsoft.

(c) 2003 www.CAD.de