Re: Memory limitation

On 2006-10-26, Rob Kennedy <me3@xxxxxxxxxxx> wrote:
This requires that you stay away from pointer arithmetic
on signed integers. If you want to use /3GB you should also use fastmm and
enable the correct switches (see usage section of readme file).

Of course, avoiding signed pointer arithmetic and using FastMM are good
ideas even if you don't need 3 GB of address space.

Why? I tried FastMM in two projects, and both slowed down significantly.

Be wary to change to fastmm if your apps might have (inadvertedly) been
tuned to the old memmgr.

.

Relevant Pages

  • Re: Memory limitation
    ... on signed integers. ... If you want to use /3GB you should also use fastmm and enable the correct switches (see usage section of readme file). ... avoiding signed pointer arithmetic and using FastMM are good ideas even if you don't need 3 GB of address space. ... As I understand it, when used as the IDE's memory manager, it also fixes some of Delphi's bugs. ...
    (comp.lang.pascal.delphi.misc)
  • Re: Memory Manager Test Results
    ... It appears as if Task Manager ... I have measured the VM Usage using the Win32 API call "GlobalMemoryStatus", ... A cursory inspection of the memory map provided by the FastMM ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: FastMM4 - lockup
    ... the server just locked the requests stopped being processed the cpu = 0 ... usage etc.... ... Could you please try FastMM 4.48? ...
    (borland.public.delphi.language.basm)