[THIN] Re: Quick PAE question
- From: "Joe Shonk" <joe.shonk@xxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Fri, 12 Jan 2007 11:52:50 -0700
It's not all that bad. It does allow for the unused memory that the
Servers (not just IBM) grab for PCI-X, etc to be remapped. The bad thing
about PAE is it takes away kernel memory space and processing overhead
because the OS now has to create a table, map and track that memory.
It's a hardware thing, and not really an OS thing. The 3.2 gigs is what is
reported when the system POSTs.
Joe
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Jay P. Moock
Sent: Friday, January 12, 2007 11:40 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Quick PAE question
Definitely a bad thing unless the app supports it (such as SQL with AWE
enabled).
As far as the 4 vs 3.2/3.5 issue, I've seen it caused by differences between
OS's (Win2k would see less than Win2k3), as well by differences in Video
cards (obviously this shouldn't be the case with Blades). I would check the
BIOS settings on servers that do differ, because I seem to recall that there
are certain settings that will allow a video card to steal memory from the
system, but I could be mistaken.
_____
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Michael Pardee
Sent: Friday, January 12, 2007 1:24 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Quick PAE question
I don't remember the final answer, but was /PAE a good thing or a bad thing?
We have a couple hundred IBM HS20 Blades, and on some Blades that OS sees
all 4GB of memory and on other it may see 3.2GB or 3.5GB of memory. Same
BIOS version on most. Adding /PAE we see it all but for some reason I
remember this being a bad thing instead of a good thing to do.
Windows2003 Standard Edition with SP1.
Thanks in advance.
--
Michael Pardee
www.blindsquirrel.org
Other related posts:
