ADSM-L

Re: Dwindling Performance

2004-01-15 17:08:10
Subject: Re: Dwindling Performance
From: Ben Bullock <bbullock AT MICRON DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Jan 2004 15:07:25 -0700
        I ~LOVE~ to hear words like that  ;-)

        BUY MORE MEMORY.... BUY MORE MEMORY... YOU ARE FEELING VERY
SLEEPY....

Ben
(FYI, I work for Micron, a DRAM manufacturer) 
http://www.crucial.com or http://www.micron.com

Before I get inundated with "don't solicit" flame-mail, I'm just kidding
guys.... :-)


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Chris Murphy
Sent: Thursday, January 15, 2004 2:57 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Dwindling Performance


<snip>

Memory is so cheap that you can afford to throw lots of it at it.

> I'm running TSM 5.1.8 on Win2K with 2G
>RAM.

Hi Dwight,

I wanted to throw out one note of caution.  I completely agree with
Roger: memory is too cheap to rob your system of it!  However, you said
you are running your TSM server on a Windows 2000 box.  Remember,
Windows limits application memory space to 2GB.  This can be increased
to 3GB with a startup option at the expense of some operating system
memory spaces.  (i.e. use it carefully!).  Thus, you cannot allocate all
2GB to bufferpool cache as TSM still needs additional space for object
creation, I/O buffering, and its own execution.  We have found that we
could only safely allocate 512-768MB to the bufferpool.  If we incerased
it beyond that, TSM would dump (go down HARD) when under load.  While
our DB is rather small (20GB - 40%
utilized) we still get a hit of 99.9%.

Other options are: Use different OS, use an Itanium-class server, talk
IBM into adding AWE support when they write/compile TSM for windows
(least likely I think <8) ).

HTH

Chris Murphy
IT Network Analyst
Idaho Dept. of Lands
(208) 334-0293

<Prev in Thread] Current Thread [Next in Thread>