Hello Peter,

13 Nov 99 14:59, Peter Knapper wrote to Eddy Thilleman:

 PK> There was a fundamental change in the logic of the USE of SWAPPER.DAT
 PK> somewhere between V2.0 and V2.11 but I can't remember enough of the
 PK> details (it was too long ago) of when all this changed.

I remember a change in swapping pages from .DLL files used by the system
(swapping when previously those pages where not swapt but kept in memory, most 
noticeable on systems with 6 MB RAM for example, barely enough memory to run
OS/2).

PK> The main change was that a PAGE in memory that was from the EXECUTABLE
PK> part of a program that NEVER altered, was written to the SWAP file
PK> just ONCE, and subsequently was never written again. This provided a
PK> small performance improvement on systems that were doing a lot of
PK> swapping.

I don't remember that. I'm not saying you're wrong, just that I don't remember 
this. :)

PK> No, you can't load pages DIRECTLY from the .EXE file itself, the .EXE
PK> file format does not contain an EXACT memory print of what that
PK> application looks like once it is loaded into memory. The only place
PK> such a print could be taken is directly from memory AFTER the .EXE is
PK> loaded.

OK, I forgot about that.

PK> Interestingly, I have been doing a bit of work with NT lately, and of
PK> course I started making comparisons.........;-) One of the first
PK> things I noticed is that NT DEFINATELY bogs down on swap file
PK> performance once your memory is over-committed, even if its only by a
PK> small amount. On the other hand, the OS/2 SWAP file can be quite large
PK> and yet performance seems to be excellent by comparison, barely
PK> noticeable.

This shows how good OS/2 is. :)

  Greetings   -=Eddy=-        email: eddy.thilleman@net.hcc.nl

... Forget love. I'd rather fall into chocolate.
--- GoldED/2 3.0.1