You should be aware that the T2000 is great for multithreaded applications.
Each backup is a single thread. Therefore, if you have a large backup you are
doing across the network, the T2000 may not be the best. admittedly it was with
TSM, but we found a large backup ran slower on the T2000 than it did when the
TSM server was on an AIX box. The reason being that an individual core was not
up to the mark. having said that, IMNSHO, that backup should've been LAN-free
anyway.
Just something to keep in mind.Siobhán> Date: Tue, 29 Apr 2008 04:12:40 +0300>
From: yaron AT ARISTO.TAU.AC DOT IL> Subject: Re: [Networker] recommendations
for networker server upgrade> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU> > Yaron
Zabary wrote:> > > . A single floating-point unit for all 24 logical CPUs. I
checked > > Networker with Sun's cooltst tool > >
(http://cooltools.sunsource.net/cooltst/) on a 280R and it came up as > >
'yellow' (FP: YELLOW (FP Component may be too high (2.56%). Further > >
checking required.)) which means that it might be an issue, although I > >
didn't notice any problem during the last couple of weeks.> > For the sake of
completeness, I publish the result of the cooltst > tool (v3) during the
nightly incremental backups. The results below > indicate that the T1
processors (T1000/T2000) are probably suitable for > Networker workloads.> > #
./cooltst.pl> Beginning observations for 5 minutes> CoolThreads Selection Tool
(cooltst) version 3.0> Copyright © 2008 Sun Microsystems, Inc. All rights
reserved> Use is subject to license terms.> > Cooltst observes a running
workload and applies various heuristics> to assess whether that workload may be
suitable for a Sun Fire> T1000/T2000/T5x20 system, to help you judge how much
effort to put> into a feasibility study which might include porting,
prototyping,> and/or performance measurement of your applications. Cooltst is>
NOT a system sizing or capacity planning tool, and the rough> approximations
used internally in cooltst should not substitute> for detailed performance
analysis.> > > System Configuration> > Host name legato.tau.ac.il> System name
SUNW,Sun-Fire-T1000> Effective UID 0> Cooltst version 3.0> OS Solaris> OS
release 5.10> OS version Generic_127111-11> Distro Solaris> BIOS/PROM OBP
4.28.1 2008/02/11 13:04> Memory 3968 MB> Chip UltraSPARC-T1> MHz 1000>
Architecture SPARC> # of Virtual CPUs 24> P0: 1000 MHz UltraSPARC-T1> P1: 1000
MHz UltraSPARC-T1> P2: 1000 MHz UltraSPARC-T1> P3: 1000 MHz UltraSPARC-T1> P4:
1000 MHz UltraSPARC-T1> P5: 1000 MHz UltraSPARC-T1> P6: 1000 MHz UltraSPARC-T1>
P7: 1000 MHz UltraSPARC-T1> P8: 1000 MHz UltraSPARC-T1> P9: 1000 MHz
UltraSPARC-T1> P10: 1000 MHz UltraSPARC-T1> P11: 1000 MHz UltraSPARC-T1> P12:
1000 MHz UltraSPARC-T1> P13: 1000 MHz UltraSPARC-T1> P14: 1000 MHz
UltraSPARC-T1> P15: 1000 MHz UltraSPARC-T1> P16: 1000 MHz UltraSPARC-T1> P17:
1000 MHz UltraSPARC-T1> P18: 1000 MHz UltraSPARC-T1> P19: 1000 MHz
UltraSPARC-T1> P20: 1000 MHz UltraSPARC-T1> P21: 1000 MHz UltraSPARC-T1> P22:
1000 MHz UltraSPARC-T1> P23: 1000 MHz UltraSPARC-T1> OS release detail:>
Solaris 10 8/07 s10s_u4wos_12b SPARC Copyright 2007 Sun Microsystems, > Inc.
All Rights Reserved. Use is subject to license terms. Assembled 16 > August
2007> > Workload Measurements> > Observed system for 5 min> in intervals of 60
sec> Cycles 7200453096552> Instructions 71970711225> CPI 100.05 **> FP
instructions 653543> Emulated FP instructions 0> FP Percentage 0.0%> The
following applies to the measurement interval with the> busiest single thread
or process:> Peak thread utilization at 2008-04-29 03:34:08> Corresponding file
name 1209429248> CPU utilization 19.8%> Command nsrmmd> PID/LWPID 11368/1>
Thread utilization 3.7%> More detail on processes and threads is in
data/process.out> > **Cycles per Instruction (CPI) is not comparable between
UltraSPARC> T1 and T2 processors and conventional processors. Conventional>
processors execute an idle loop when there is no work to do, so> CPI may be
artificially low, especially when the system is> somewhat idle. The UltraSPARC
T1 and T2 "park" idle threads,> consuming no energy, when there is no work to
do, so CPI may> be artificially high, especially when the system is somewhat
idle.> > Advice> > During the observation of the highest utilization thread, a
fairly> low overall CPU utilization of 19.8333333333334% was seen. Are you sure
that> the workload of interest was running on the system during the time>
cooltst was running? If not, please run cooltst again while your> workload is
active.> > If your workload was running during this observation, then take>
cooltst's advice with this caveat. If you expect your workload to> increase to
higher levels, do you expect it to do so by adding> additional threads, as is
common, or do you expect it to add more> work to the existing single thread, as
sometimes happens? If your> response time criteria are being met, then even if
a single thread> is responsible for most of your CPU consumption, you should
still> get acceptable performance from a a system based on the UltraSPARC> T1
processor (i.e. Sun Fire/SPARC Enterprise T1000, T2000, Sun Blade> T6300) or a
system based on the UltraSPARC T2 processor (i.e. SPARC> Enterprise T5120,
T5220, Sun Blade T6320), with excess throughput> capacity for future growth.
But if response time is marginal and> workload growth is expected to be in a
single thread, then a CMT> system may not be appropriate.> > > Floating Point
GREEN> Observed floating point content was not excessive for> an UltraSPARC T1
processor. Floating point content is not> a limitation for UltraSPARC T2.> >
Parallelism GREEN> The observed workload has sufficient threads of execution
to> efficiently utilize the multiple cores and threads of an> UltraSPARC T1 or
UltraSPARC T2 processor.> > This information is saved in 'cooltst.out'> For
problem reporting, please also include cooltst.err and> a tar archive of the
'data' directory> 3.48u 4.48s 5:08.59 2.5%> > -- > > -- Yaron.> > To sign off
this list, send email to listserv AT listserv.temple DOT edu and type "signoff
networker" in the body of the email. Please write to networker-request AT
listserv.temple DOT edu if you have any problems with this list. You can access
the archives at http://listserv.temple.edu/archives/networker.html or> via RSS
at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
_________________________________________________________________
Are you paid what you're worth? Find out: SEEK Salary Centre
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau%2Fcareer%2Dresources%2Fsalary%2Dcentre%2F%3Ftracking%3Dsk%3Ahet%3Asc%3Anine%3A0%3Ahot%3Atext&_t=764565661&_r=OCT07_endtext_salary&_m=EXT
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
