[Coco] OS9 vs MS Win

[davidlinsley at gmail.com]

“one re-entrant application module into RAM, just increase the
link count on each launch and set a separate data space for each”


Hi Rogelio,


This is how Windows works too. The memory pages backing an image (module) are shared across all processes, unless that process tries to modify the page (for example, writing to a global variable). At that point it gets its own private copy of that page.



Cheers,

David.







From: Rogelio Perea
Sent: ‎Wednesday‎, ‎February‎ ‎26‎, ‎2014 ‎6‎:‎20‎ ‎AM
To: coco at maltedmedia.com





I work with AutoCAD a lot on the day job, usually open up drawings out of a
VSS database and as I loaded 3 drawings to view today I wondered what was
going on within Windows as way of memory usage. The Weven Task Manager
confirmed that on each drawing pull, a new acadlt.exe process is loaded
eating away roughly 100 MB of memory space.

Makes me wonder how MS Windows would be if it managed itself closer to how
OS9 does: one re-entrant application module into RAM, just increase the
link count on each launch and set a separate data space for each. Too
efficient. Utopia.

With 8 gigs of RAM in the computer, I guess no one needs to care about the
RAM footprint anymore.

Back to the ol' grind.


-- RP

--
Coco mailing list
Coco at maltedmedia.com
http://five.pairlist.net/mailman/listinfo/coco