Doesn't appear to be a network issue. All packets presented appear to have been sent without delay of complaints about lack of buffer space. That points at disk (which is, assuming a properly configured network) usually the bottleneck anyway. A couple of suggestions: use iperf/netperf between the hosts to verify the network will go fast for some value of fast (the next most likely bottleneck is DDR2 ram at 6.4 gigs per second and/or the PCI bridge chips on the motherboard) at least faster than 380 megabits per second (we can achieve 995 megabits per second across 3000 mile gigabit paths with properly tuned linux boxes so this shouldn't be an issue). Then you are in to disk I/O benchmark software such as bonnie to see what your disk subsystem read speed is (I'd guess around 380 megabits per second :-)). This is limited by spindle seek time primarily and a few other factors such as thermal recalibration. Performance is a serial process, it is only as fast as the slowest point in the path.
Peter Van Epp / Operations and Technical Support Simon Fraser University, Burnaby, B.C. Canada On Fri, Oct 03, 2008 at 11:18:44AM -0400, Levesque, Jeff wrote: > Hi, > > I was hoping someone could help me figure out why I'm > getting the numbers I have. I'm using a 10Gb fiber link but I can't get > any replays to even 1Gb. Output and system specs are listed below. > > > > Thanks, > > - Jeff > > > > [EMAIL PROTECTED] tcpreplay-3.3.2]# tcpreplay -i eth2 -t -K -l 1000 -q > /shared/nfs.pcap > > Actual: 563000 packets (57654000 bytes) sent in 1.13 seconds > > Rated: 50978920.0 bps, 388.94 Mbps/sec, 497816.84 pps > > > > Statistics for network device: eth2 > > Attempted packets: 563000 > > Successful packets: 563000 > > Failed packets: 0 > > Retried packets (ENOBUFS): 0 > > Retried packets (EAGAIN): 0 > > [EMAIL PROTECTED] tcpreplay-3.3.2]# tcpreplay -i eth2 -t -K -l 5000 -q > /shared/nfs.pcap > > Actual: 2815000 packets (288270000 bytes) sent in 5.91 seconds > > Rated: 48713524.0 bps, 371.65 Mbps/sec, 475694.88 pps > > > > Statistics for network device: eth2 > > Attempted packets: 2815000 > > Successful packets: 2815000 > > Failed packets: 0 > > Retried packets (ENOBUFS): 0 > > Retried packets (EAGAIN): 0 > > > > System Specs: > > - Intel Xeon 5130 x 2 > > - 4GB of RAM > > - 250GB SATA HDD x 2 (RAID 1) > > - Intel Dual 10Gigabit NIC PCI-E 8x (82598EB) (tcpreplay only) > > - Intel Quad NIC PCI-E 4x (82571EB) (management only) > > > > I have 2 of those boxes linked with the 10Gb links. I've also tried > linking 2 10Gb links together on one box and using tcpreplay with a 2 > NIC setup and saw the same results. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Tcpreplay-users mailing list > Tcpreplay-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tcpreplay-users > Support Information: http://tcpreplay.synfin.net/trac/wiki/Support ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Tcpreplay-users mailing list Tcpreplay-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tcpreplay-users Support Information: http://tcpreplay.synfin.net/trac/wiki/Support
