click performance

[Amit Dror]

Robert,

The cards we use are also Pro/1000 F (although connected to a 33MHz PCI
bus).

Attached is the configuration file.

What is the CPU speed on the machine you are using ?

Thanks,


Amit

> -----Original Message-----
> From: Robert Morris [mailto:rtm at amsterdam.lcs.mit.edu]
> Sent: Fri, June 15, 2001 3:46 PM
> To: Amit Dror
> Cc: click at amsterdam.lcs.mit.edu
> Subject: Re: click performance
>
>
> Amit,
>
> While Click can receive or send that fast, it can't do both. I think
> it can only forward at about half that rate.
>
> We use a machine with a 64bit/66mHz PCI bus.
>
> We also use the 66 mHz PCI version of the e1000, called the
> "Pro/1000 F
> Server Adapter" (note the "F"), model number PWLA8490SX.
>
> If you have model PWLA8490, you have a card with a 33 mHz PCI
> interface.  It sends a lot slower than the PWLA8490SX, but I think it
> receives at about the same rate.
>
> Robert
>
> > From: "Amit Dror" <amit at checkpoint.com>
> > To: "'Robert Morris'" <rtm at amsterdam.lcs.mit.edu>
> > Cc: <click at amsterdam.lcs.mit.edu>
> > Subject: RE: click performance
> > Date: Fri, 15 Jun 2001 16:24:18 +0200
> > Importance: Normal
> >
> > Robert,
> >
> > The following line is taken from the Click Change
> Log/Software History
> > Version 1.2.0:
> > "Added a polling Intel EEPro 1000 gigabit driver, which can
> receive or send
> > up to 1.3 million 64 byte packets per second."
> >
> > We are using Smartbits system to generate/measure the
> forwarding rate.
> > Smartbits should be able to perform up to full gigabit capacity.
> >
> > I don't have the configuration file accessible at the
> moment, but it was
> > generated by the make-ip-conf.pl script.
> >
> > I'm starting to suspect that the difference may be caused
> because of the PCI
> > bus. We are using a single 64bit/33MHz PCI bus.
> >
> > Thanks,
> >
> >
> > Amit
> >
> > > -----Original Message-----
> > > From: Robert Morris [mailto:rtm at amsterdam.lcs.mit.edu]
> > > Sent: Thu, June 14, 2001 6:14 PM
> > > To: Amit Dror
> > > Cc: click at amsterdam.lcs.mit.edu
> > > Subject: Re: click performance
> > >
> > >
> > > Amit,
> > >
> > > Where did you see a report of Click forwarding 1.3 million packets
> > > per second?
> > >
> > > What are you using to generate the packets? What are you using
> > > to measure the forwarding rate?
> > >
> > > Can you send us the exact Click configuration you are using?
> > >
> > > Thanks,
> > > Robert
> > >
> > > > From: "Amit Dror" <amit at checkpoint.com>
> > > > To: <click at amsterdam.lcs.mit.edu>
> > > > Subject: click performance
> > > > Date: Thu, 14 Jun 2001 19:05:42 +0200
> > > > Importance: Normal
> > > >
> > > > Hi,
> > > >
> > > > we have set-up an environment with a click router and Intel
> > > EEPro 1000
> > > > gigabit cards.
> > > >
> > > > Running a test of 64 byte packet stream we have reached
> > > only 325,000 packets
> > > > per second with the following hardware configuration:
> > > >
> > > > IBM Netfinity 4500R
> > > > Dual Intel PIII 1000Mhz (booted UP kernel) , 256MB RAM
> > > > 2 x Intel PRO/1000 NICs
> > > >
> > > > The click router is running a simple IP router
> > > configuration generated by
> > > > make-ip-conf.pl
> > > >
> > > > As this is quite far from the reported 1.3 million 64 byte
> > > packets per
> > > > second result  we try to understand what causes the difference.
> > > >
> > > > Is it possible to get the hardware configuration in which
> > > the 1.3 million 64
> > > > byte packets per second was measured ?
> > > >
> > > > Do you have any idea about what may cause this difference ?
> > > >
> > > > Thanks,
> > > >
> > > >
> > > > Amit Dror, Software Developer,
> > > > Check Point Software Technologies Ltd. http://www.checkpoint.com
> > > > Phone: +972-3-7534532, Fax: +972-3-7534893
> > > >
> > > ==============================================================
> > > ===========
> > > > This message may contain confidential and/or proprietary
> > > information, and
> > > > is intended only for the person / entity to whom it was
> originally
> > > > addressed. The content of this message may contain
> private views and
> > > > opinions which do not constitute a formal disclosure or
> > > commitment unless
> > > > specifically stated.
> > > >
> > >
> > >
> >
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: router.click
Type: application/octet-stream
Size: 2218 bytes
Desc: not available
Url : https://amsterdam.lcs.mit.edu/pipermail/click/attachments/20010617/5e8aca47/router.obj