Proliant ML 570 G4 memory allocation

[Stephen Tomasco]

The current server has 8 gigs on the board and for some reason the server never goes over 3.90 gigs on OS production (server 2003 enterprise edition sp 2).

config
4*1024
2*2048
all Dimms on Board 1

any thoughts?

[cnb]

See this thread:

http://forums13.itrc.hp.com/service/forums/questionanswer.do?admit=109447627+1244051603353+28353475&threadId=1019730

Also check out the quickspec memory config chart here:

http://h18004.www1.hp.com/products/quickspecs/12474_na/12474_na.html#Memory

hth,

[Stephen Tomasco]

hello cnd,
the os is seeing the 8 gigs but it never exceeds 3.90 gigs of use

I did just notice this
Serial presence detect (SPD) information - DIMM 5, Card 1
Memory type SDRAM DDR2
DIMM Description
Spare Part Number
Single-Bit Threshold Exceeded Status Correctable error threshold exceeded
Multi-Bit Status No DIMM errors detected
Single-Bit Threshold Count 1
Multi-Bit Count 0

Does 'Correctable error threshold exceeded' this mean I need to replace it?

The server is running SQL 2005 with 1.6 gigs of RAM and Business Objects 11.5 using various amounts of the rest of the 1.4 gigs and there is never more the 5 analyst on the machine and the BO application runs very slow but the hardware level (processors x4 and memory 8gigs) never spike at all. I am confused at this point. I am in the process of removing SQL which will give the 1.6 gigs back to Business Objects but I just am drawing a blank on the memory allocation as to why it never spikes over 3.9 gigs.

[cnb]

What are your BOOT.INI switches set at? Are you using PAE and AWE per the KB articles?

http://support.microsoft.com/kb/283037

http://support.microsoft.com/kb/274750

For the dimm issue see this guide:

http://www.icare.hp.com.cn/TechCenter_StaticArticle/33464/38078.pdf

hth,

Pls assign points if you find any of this useful:
http://forums11.itrc.hp.com/service/forums/helptips.do?#22

[Stephen Tomasco]

Here is the boot.ini and it appears the /pae is enabled. what is the /noexcute=optout?

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /fastdetect /PAE /NoExecute=OptOut

I have to speak with our database team about the /awe for sql

[Stephen Tomasco]

/noexcute = DEP which I disabled to see if this would increase performance. I did nothing from a end user perspective.

Maybe Business Objects is the problem. I think removing SQL maybe the best course of corrective action at this point.