Statalist


[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

Re: st: Does Windows 2003 Server Provide a means to use more than 2GB of memory?


From   "Thomas Jacobs" <thomasjacobs@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   Re: st: Does Windows 2003 Server Provide a means to use more than 2GB of memory?
Date   Wed, 9 Jul 2008 08:48:17 -0500

Thanks to Caveman and Jeph for the replies.

I should mention that I am on a tight budget and have access to the
Windows Server 2003, Standard Edition software for free through the
Microsoft Dreamspark program and have not researched what it would
cost to buy a stand alone copy of XP Pro 64 but would guess it will be
close to the cost of the new machine unless I were OEM.

I struggled through the lengthy posts in the second link that Caveman
provided as most of the commentary relates to using more than 4GB
which is not something I will even try as it is the limit for Windows
Server 2003, Standard Edition (I understand that all 32 bit systems
have an addressable limit of 4GB but Enterprise and Datacenter
versions evidently work around this to make more RAM available to
applications, assuming the application is written to recognize it).
It appears that there is not a lot of difference between the Server
operating system and the XP Pro I had read about in past Stata posts
and memory limits.  It appeared that one can set a switch in the
Server operating system for changing the allocation of the 4GB of
memory from the default of 2GB for applications and 2GB for the memory
kernel to 1GB for the kernel and 3GB for applications (/3GB).  This
would imply that one could reach 3GB for Stata.  However, a relevant
comment is this from the lengthy post section:

Here's the main problem with the 3GB switch: Applications must be
specifically compiled to look for and recognize the fact that they can
use 3GB instead of 2GB of memory. Right now the only apps that I know
of that have this intelligence are SQL Server and Exchange Server. So
for "regular" desktop apps, they'll continue to use a 2GB memory
space, and the kernel will use 1GB, and you'll have a 1GB "hole" right
in the middle of everything!

Thus, I am left wondering if Stata will use this extra GB.  If anyone
has experience and can comment I would appreciate it before I go to
the trouble of learning how to install and get up to speed on Windows
Server 2003.  Otherwise I will just continue to use Windows XP and pay
for a machine with only 2GB of RAM.

Tom


On Wed, Jul 9, 2008 at 8:25 AM, Jeph Herrin <junk@spandrel.net> wrote:
> If you are going to the trouble of buying a new machine, you
> might as well look at using XP64 (64-bit XP); it can access up
> to 64GB RAM, and is probably more usable than Server 2003.
> Stata Corp will upgrade your license to 64bit for only a token
> fee.
>
> hth,
> Jeph
>
>
> Thomas Jacobs wrote:
>>
>> I am running Stata SE 10 under Windows XP and have seen more than
>> once, as I understand it, in this list that physical memory in excess
>> of 2GB cannot be accessed due to limitations of Windows XP.  I have
>> access to Windows Server 2003 Standard Edition which claims to provide
>> access to up to 4GB.  Before I go to the trouble of buying a machine
>> with 4GB of RAM can anyone share whether this will work?  Will Stata
>> SE 10 be able to access more than 2GB of RAM running on Windows Server
>> 2003?  Thanks.
>>
>> Tom
>>
>> --
>> Thomas Jacobs
>> *
>> *   For searches and help try:
>> *   http://www.stata.com/support/faqs/res/findit.html
>> *   http://www.stata.com/support/statalist/faq
>> *   http://www.ats.ucla.edu/stat/stata/
>>
> *
> *   For searches and help try:
> *   http://www.stata.com/support/faqs/res/findit.html
> *   http://www.stata.com/support/statalist/faq
> *   http://www.ats.ucla.edu/stat/stata/
>



-- 
Thomas Jacobs
*
*   For searches and help try:
*   http://www.stata.com/support/faqs/res/findit.html
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/



© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index