RE: disk cache battery story

I don't know the specific answer....

But consider the rate of improvement of disk vs. the rate of improvement
in CPU's.

Disks just haven't kept up, thus the need to add caching.

HTH,

Charles Wilt
--
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121
  

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Steve Richter
> Sent: Tuesday, February 28, 2006 6:04 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: disk cache battery story
> 
> On 2/28/06, Larry Bolhuis <lbolhuis@xxxxxxxxxx> wrote:
> > It needs to charge the battery long enough to trust the 
> bugger!! This
> > would be normal.
> 
> that makes sense.  I would not have thought the system charges the
> battery as well as drawing on it.
> 
> I am curious when the disk controller cache was first used on the
> as400.  The single level store seems to benefit greatly from having
> the disk cache. Assuming the s/38 did not have it, how could that
> system have performed as well as it did without a cache?
> 
> -Steve
> 
> 
> 
> >
> > Same battery from Batteries Plus is about $15.
> >
> >  - Larry
> >
> > Steve Richter wrote:
> > > I had to replace the battery on the disk controller of my 
> 170 today.
> > > After the battery died on thursday I did a bunch of compiles to
> > > measure how slow the system had gotten. Compiles were taking 20
> > > seconds each.
> > >
> > > Part number 91H3968. $75!!
> > >
> > > It was easy to replace the battery pack. Pull the card 
> from the PCI
> > > slot on the 170. ( is that the PowerPC CPU on that same 
> card?  It has
> > > powerPC printed on it, but does not appear very big. ).  
> Upen the cage
> > > the battery is in, snap in the new battery, put the card 
> back in its
> > > slot.
> > >
> > > Funny thing is after IPLing the system the error message 
> was gone from
> > > qsysopr but my compiles were still taking 20 seconds 
> each.  Did about
> > > 20 compiles and they were all slow. Now I am back on the system 30
> > > minutes later and the compiles are running fast again. 
> About 4 seconds
> > > each.   For a reason I cant explain, the system took a 
> little while
> > > for the disk cache memory to start working.
> > >
> > > -Steve
> > >
> > >
> >
> > --
> > Larry Bolhuis                   IBM eServer Certified 
> Systems Expert:
> > Vice President                    iSeries Technical Solutions V5R3
> > Arbor Solutions, Inc.             iSeries LPAR Technical 
> Solutions V5R3
> > 1345 Monroe NW Suite 259          iSeries Linux Technical 
> Solutions V5R3
> > Grand Rapids, MI 49505            iSeries Windows 
> Integration Technical
> > Solutions V5R3
> >                                IBM eServer Certified 
> Systems Specialist
> > (616) 451-2500                    iSeries System Administrator for
> > OS/400 V5R3
> > (616) 451-2571 - Fax              AS/400 RPG IV Developer
> > (616) 260-4746 - Cell             iSeries System Command 
> Operations V5R2
> >
> >  If you can read this, thank a teacher....and since it's in English,
> > thank a soldier.
> >
> > --
> > This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
> 
> -- 
> This is the Midrange Systems Technical Discussion 
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
>