ADSM-L

Re: performance scaling question

2006-01-06 03:35:32
Subject: Re: performance scaling question
From: Pétur Eyþórsson <petur.e AT NYHERJI DOT IS>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 6 Jan 2006 08:33:24 +0000

Adding a second one, has been my experience. and i recomend it. I don´t think you will see any perfomance enhancement with upgradeing your cpu from 2.8 to 3.2 in TSM.

 

 
"It´s better to aim at perfection and miss than it is to aim at imperfection and hit it"
Founder Thomas J. Watson

Kær kveðja / Best regards,
Pétur Eyþórsson  · Tæknilegur ráðgjafi eServer & Storage · Tivoli Advanced Storage Solutons Techical Expert
 · MCSE · SNIA Professional  ·  SNIA FC-SAN Practitioner  ·  IBM C AIX S · TSM CP · TSRM CP · TASS DP · IBM SAN P
Sími/tel: +354 569-7700 · GSM: +354 863-0560
www.nyherji.is




Troy Frank <Troy.Frank AT UWMF.WISC DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

05.01.2006 21:20
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

To
ADSM-L AT VM.MARIST DOT EDU
cc
Subject
[ADSM-L] performance scaling question





My server is an IBM x235 with a single Xeon 2.8ghz (533mhz fsb), running
windows2003.  I've noticed that the cpu gets pretty consistently pegged
every night during backups, and I was wondering what would do more
good.... replacing the single 2.8 with a 3.2, or leaving the 2.8 and
adding a second one?



Confidentiality Notice follows:

The information in this message (and the documents attached to it, if any)
is confidential and may be legally privileged. It is intended solely for
the addressee. Access to this message by anyone else is unauthorized. If
you are not the intended recipient, any disclosure, copying, distribution
or any action taken, or omitted to be taken in reliance on it is
prohibited and may be unlawful. If you have received this message in
error, please delete all electronic copies of this message (and the
documents attached to it, if any), destroy any hard copies you may have
created and notify me immediately by replying to this email. Thank you.

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