high performant TRex (UCS note for future)

33 views
Skip to first unread message

Matt Callaghan

unread,
May 8, 2018, 11:26:45 AM5/8/18
to TRex Traffic Generator
What does this statement mean from the documentation?

https://trex-tgn.cisco.com/trex/doc/trex_manual.html#_hardware_recommendations

NOTE: A high-end UCS platform is not required for operating TRex in its current version, but may be required for future versions.

We are investing in TRex on COTS. Wondering if this means there is risk that in the future TRex may require Cisco UCS hardware?

hanoh haim

unread,
May 9, 2018, 3:21:49 AM5/9/18
to Matt Callaghan, TRex Traffic Generator
Hi Matt,
No risk. it just a question of performance. 

thanks,
Hanoh

--
You received this message because you are subscribed to the Google Groups "TRex Traffic Generator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trex-tgn+unsubscribe@googlegroups.com.
To post to this group, send email to trex...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/trex-tgn/48312f3a-06e1-4dbb-a37b-52e1a5fbcad1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Hanoh
Sent from my iPhone

Matt Callaghan

unread,
May 9, 2018, 3:42:50 PM5/9/18
to TRex Traffic Generator
OK so good for the future. But what do we mean specifically by "question of performance"?

Maybe we should quantify "performance" ((>100Gbps?))

I can think of:
 A) TRex may in the future only support high performant generation on Cisco UCS hardware
 B) TRex guarantees regression of high performant generation only on Cisco UCS hardware
 C) Cisco may not actively support (and will not actively hinder) TRex on COTS for high performant generation

Andrew Theurer

unread,
May 9, 2018, 4:11:07 PM5/9/18
to Matt Callaghan, TRex Traffic Generator
On Wed, May 9, 2018 at 2:42 PM, Matt Callaghan <mcallagha...@gmail.com> wrote:
OK so good for the future. But what do we mean specifically by "question of performance"?

Maybe we should quantify "performance" ((>100Gbps?))

I can think of:
 A) TRex may in the future only support high performant generation on Cisco UCS hardware
 B) TRex guarantees regression of high performant generation only on Cisco UCS hardware
 C) Cisco may not actively support (and will not actively hinder) TRex on COTS for high performant generation

​Unless UCS ends up using proprietary network adapters not available elsewhere, and other generally available adapters become unsupported on TRex, then I don't think you have anything to worry about.

We run TRex on Intel Haswell-EP (2 generations old) based 2-socket systems​ with 4 x Intel XVV710 2x25 Gb adapters, and we can sustain 111-Mpps with Rx-queue filtering (so we can differentiate 1 packet type from another)  We still have plenty of CPU left, and the only eventual restriction is probably PCI lanes.  I expect we could go to 6 or 7 dual port adapters if we needed to.


On Wednesday, May 9, 2018 at 3:21:49 AM UTC-4, Hanoch Haim wrote:
Hi Matt,
No risk. it just a question of performance. 

thanks,
Hanoh

--
You received this message because you are subscribed to the Google Groups "TRex Traffic Generator" group.
To unsubscribe from this group and stop receiving emails from it, send an email to trex-tgn+unsubscribe@googlegroups.com.
To post to this group, send email to trex...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages