ProLiant Servers (ML,DL,SL)
1753277 Members
5487 Online
108792 Solutions
New Discussion

Re: PROLIANT ML 150 G3 additional RAM with RAM disk

 
PP63
Occasional Contributor

PROLIANT ML 150 G3 Additonal RAM with RAM disk

Hello everybody

Does it make sence to extend RAM of HP ProLiant ML150 G3 (WS2003 SBS, MS SQL2005) above current 4GB we have to make a RAM disk there and to locate Memory SWAP file on such a RAM disk rather then on 72GB SAS HDD?

Can x86 processor of ML150 G3 establish and operate RAM disk in RAM above 4GB at all?

Thnx for advices and opinia.

Petr P.

 

 

P.S. This thread has been moved from Community Feedback & Suggestions to ProLiant Servers (ML,DL,SL). - Hp Forum Moderator

3 REPLIES 3
Dennis Handly
Acclaimed Contributor

Re: PROLIANT ML 150 G3 additional RAM with RAM disk

>locate Memory SWAP file on such a RAM disk rather then on 72GB SAS HDD?

 

This just seems silly.  If you have more RAM, just use it as memory, so you don't swap at all.

You use RAM disk to replace files, not swap.

PP63
Occasional Contributor

Re: PROLIANT ML 150 G3 additional RAM with RAM disk

Thank you Dennis for your reaction>

 

PROLIANT ML 150 G3 has a 32-bit (x86) processor.
My understanding was that

1/ 32 bit processor can not address RAM above 2^32 ie 4GB

2/ the WS2003 system uses a paging file on a disk as if it were RAM (Virtual memory), I called it SWAP file.

3/ the idea was to put this SWAP file on a RAM drive rather than HDD

 

My question was

a/  Can a RAM Disk be installed in the area above 4GB on 32-bit systems?
One would expect NO, unless the 4GB addressing issue was not a limit for RAM disk setup.

 

b/ Are there any considerations to take into account for such a setup if it was possible?

thank you.

Petr P.

Dennis Handly
Acclaimed Contributor

Re: PROLIANT ML 150 G3 additional RAM with RAM disk

>a.  Can a RAM Disk be installed in the area above 4GB on 32-bit systems?
>One would expect NO, unless the 4GB addressing issue was not a limit for RAM disk setup.

 

That would be my first guess but I'm not that familiar with x86 and what Windows can do.