Networker

Re: [Networker] Sun Hardware

2009-10-12 20:25:25
Subject: Re: [Networker] Sun Hardware
From: Vernon Harris <harriv00 AT YAHOO DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 12 Oct 2009 17:20:18 -0700
My rule of thumb is 1 LTO-3/4 needs 1ghz of cpu.  That should take care of 
drive and the overhead
of a 1ghz nic card.



----- Original Message ----
From: Joel Fisher <jfisher AT WFUBMC DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Sent: Monday, October 12, 2009 8:11:42 PM
Subject: [Networker] Sun Hardware

Hey Guys,



Can anyone give me an idea of how many lto-4 drives a T2000 or T5220
could keep streaming.



Assumptions.

Data is landed on disk(adv_file) then cloned to LTO-4 drives during the
day.

The disk is not a bottle neck.

Plenty of hbas so connectivity is not a bottleneck



Could I have say 3 landing areas and then stream to 3 LTO-4
simultaneously.  Somewhere between 120-240MB/s?



Any real world users of something like this.



I know these servers can seriously move some data, I guess my main
concern, is can they move a single stream fast enough for LTO-4 or
LTO-5?  Since any individual thread is limited to the 1.2-1.6Mhz.



Any advice here would be appreciated.



Thanks!



Joel 


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



      

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

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