| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: swapper.dat |
Andrew Belov wrote: > On Sat, 20 Mar 2004 14:43:52 -0800 (PST), Gerry Britton wrote: > > >>>OS/2 swaps some DLL's to the swapper.dat if it exists. >> >>For sure, even if you have 2G's of RAM installed, the system will >>copy the DLL;s to the swap. > > > It doesn't look this way. > > SWAPPER DAT 1048576 20.03.04 21:42 > > Shouldn't that be easier to discard the code segments and reload them > from the DLLs when necessary, rather than duplicating their code in the > swapper file? Yes, no. As in the old days as RAM was very expensive nobody has buyed enough to avoid swapping even in standard use there was the problem that in extreme requirements even system dlls had to swap out. There is the problem: reading code from DLL needs readdressing anything again whereas the swapper is an real extension of RAM. This costs more time than to read simply something back - but uses more swapper space. So the memory manager check if the relation of RAM size fits to the average use of RAM an average system needs. If RAM available is less than that the system loader writes in the initial phase some system DLLs after loading magically directly to swapper to reserve the space before anything else goes on. Makes it quicker to load them when discarding was required and they reload from its DLLs. As this itself is even an time consuming process it was a compromise between loadup time and usage time. You sees this behavior again when you shrinks your memory to only 32 MB. Your startsize is quite much too big when you have 128 MB or more RAM. 2048 is good enough and will normally never grow the swapper. But you should increas the warning time significantly. set this to 64MB or better higher - because this is on modern processors the only chance to get be warned and a chance to kill one or more memory hungry processes until there is no more room to swap out. The standard size of 2048 was good for a slow 80486. As the memory manager initiates the message but does not wait until it occures on the screen the swapper will eat any available space on disk before the system finds time to ask you if and which process you like to kill to avoid an system halt on lack of available virtual address space. While the message is sheduled to come on the screen the free space on disk shrinks continuousely - and at least much quicker now. ------------------------ Yahoo! Groups Sponsor ---------------------~--> Buy Ink Cartridges or Refill Kits for your HP, Epson, Canon or Lexmark Printer at MyInks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511 http://us.click.yahoo.com/mOAaAA/3exGAA/qnsNAA/E8folB/TM ---------------------------------------------------------------------~-> Yahoo! Groups Links To visit your group on the web, go to: http://groups.yahoo.com/group/os2user/ To unsubscribe from this group, send an email to: os2user-unsubscribe{at}yahoogroups.com Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/ ---* Origin: Waldo's Place USA Internet Gateway (1:3634/1000) SEEN-BY: 633/267 270 @PATH: 3634/1000 12 106/2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.