AW: Performance drop after upgrade to TSM 4.2.1.8

2002-01-29 Thread Rupp Thomas (Illwerke) 

Yes, last weekend.
I will give you the current numbers next monday (if Alois Alzheimer hits me
please
remind me).

Thomas Rupp

> -Ursprüngliche Nachricht-
> Von:  Mr. Lindsay Morris [SMTP:[EMAIL PROTECTED]]
> Gesendet am:  Dienstag, 29. Jänner 2002 16:33
> An:   [EMAIL PROTECTED]
> Betreff:  Re: Performance drop after upgrade to TSM 4.2.1.8
> 
> I have heard (from Sheelagh Treweek) that these benefits may only be
> temporary.  I would be interested to see how these numbers look a week
> from
> now. (I assume you did the unload/reload job quite recently.)
> 
> 
> Mr. Lindsay Morris
> CEO
> Applied System Design
> www.servergraph.com
> 859-253-8000 ofc
> 425-988-8478 fax
> 


--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

AW: Performance drop after upgrade to TSM 4.2.1.8

2002-01-29 Thread Rupp Thomas (Illwerke) 

Hi,

after UNLOADDB/LOADDB the size of our db changed from 7.1
GB to 4.8GB.
Performance is much better now: EXPIRE INVENTORY changed from 35K
entries/hour
to 105K entries/hour.
Cache hit rate went up to about 98%.

Our db was 15 months old. I think a reorg after a version upgrade is a good
thing.

Kind regards
Thomas Rupp


--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

Re: Performance drop after upgrade to TSM 4.2.1.8

2002-01-29 Thread Wholey, Joseph (TGA\\MLOL) 

How do you go about unloading and loading your db.  Is this ever really necessary.  
Shouldn't TSM manage that sort of "thing" on it's own?

-Original Message-
From: Rupp Thomas (Illwerke) [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 28, 2002 8:50 AM
To: [EMAIL PROTECTED]
Subject: AW: Performance drop after upgrade to TSM 4.2.1.8


Hi,

maybe we've got the same problem (slow performance) but on a different
platform.
We upgraded from TSM 3.7.2.0 to 4.1.1.0 and our database cache hit rate
dropped to
about 95%.
We then upgraded to TSM 4.1.5.0, changed some settings in DSMSERV.OPT - to
no
avail.
Over this weekend we defragmented (UNLOADDB/LOADDB) our database and this
seemed
to solve our problem - I can tell you more tomorrow!

We are running on an H50 with AIX 4.3.3.0.

Kind regards
Thomas Rupp



--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

Re: Performance drop after upgrade to TSM 4.2.1.8

2002-01-28 Thread Denzel, Richard van 

Ok, let me know.

Richard.

-Original Message-
From: Rupp Thomas (Illwerke) [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 28, 2002 2:50 PM
To: [EMAIL PROTECTED]
Subject: AW: Performance drop after upgrade to TSM 4.2.1.8


Hi,

maybe we've got the same problem (slow performance) but on a different
platform.
We upgraded from TSM 3.7.2.0 to 4.1.1.0 and our database cache hit rate
dropped to
about 95%.
We then upgraded to TSM 4.1.5.0, changed some settings in DSMSERV.OPT - to
no
avail.
Over this weekend we defragmented (UNLOADDB/LOADDB) our database and this
seemed
to solve our problem - I can tell you more tomorrow!

We are running on an H50 with AIX 4.3.3.0.

Kind regards
Thomas Rupp



--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

AW: Performance drop after upgrade to TSM 4.2.1.8

2002-01-28 Thread Rupp Thomas (Illwerke) 

Hi,

maybe we've got the same problem (slow performance) but on a different
platform.
We upgraded from TSM 3.7.2.0 to 4.1.1.0 and our database cache hit rate
dropped to
about 95%.
We then upgraded to TSM 4.1.5.0, changed some settings in DSMSERV.OPT - to
no
avail.
Over this weekend we defragmented (UNLOADDB/LOADDB) our database and this
seemed
to solve our problem - I can tell you more tomorrow!

We are running on an H50 with AIX 4.3.3.0.

Kind regards
Thomas Rupp



--
Dieses eMail wurde auf Viren geprueft.

Vorarlberger Illwerke AG
--

Performance drop after upgrade to TSM 4.2.1.8

2002-01-28 Thread Denzel, Richard van 

Hi All,

After upgrading serveral NT-servers from ADSM 3.1 to TSM 4.2.1.8 we've seen a giant 
drop in performance. The backup used to take around 2-hours and after the upgrade it 
takes 8 hours

The machine are all NT 4.0SP6(a) and all have local attached DDS drives. The client on 
this system is 4.2.1.15.

Has anyone seen this problem and knows about a cure for it?

Richard.

-
Richard van Denzel
High Availability & Storage Solutions
Senior Technical Consultant

Infrastructure Consulting & Integration
[EMAIL PROTECTED]

Getronics Infrastructure Solutions
Wiltonstraat 42
Postbus 1005
3900 BA  Veenendaal
tel.: 0318 - 567 100
fax:  0318 - 567 633

mobiel: 06 - 212 78 569

Building Futures on <>