SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 15 | January | 2002 ]

<< Previous Message <<


Date: Tue, 15 Jan 2002 21:52:31 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: Re: MAX HeadRAM

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

J. R. Fox wrote:
>
> He said that massive amounts of RAM could
> actually make the system more sluggish.

This is true for some older chipsets (and maybe some stupid new ones,
too). With those, memory above 256 MB used a slower hardware access
cycle *and* sometimes it wasn't cached, either.

But that's a hardware cause, not a software cause.

> something called the "Heavy Iron" effect. He said that massive
> amounts of RAM could actually make the system more sluggish.

The old mainframes didn't have "chip sets" and the memory management was
handled by the software kernel. Perhaps that's the reason (the term
"Heavy Iron" refers to mainframes, at least in *my* computer
dictionary).

I'm not familiar with the "Heavy Iron" memory slowdown effect which Ron
Higgin discussed but on a /360 model 50 with a memory configuration that
was large for the time your programs could run three to four times
*slower* when the extra memory was plugged in. The reason was pretty
darn simple but the bottom line was "yes, more memory meant you ran
slower".

> I can tell you for sure that the more RAM you have,
> the longer it will take your machine to boot up.

Yup, same here. But it's not a big difference.

- Peter

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================


<< Previous Message <<

Return to [ 15 | January | 2002 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.