Hi George,
Routing is performed in HW and you can achieved the same throughput in L3 than in L2. Because everything happens in HW, to keep that L3 throughput, you need to stay within the HW capacity of the L3 tables, otherwise slow path (CPU) may happen.
Following the link Drew gave you, you can find all the relevant information.
Looking at the first table of the DS on page 5: You have a BD8810 with c-series modules and a single MSM-48c. You have then a backplane bandwidth capacity of 24Gbps per Slot. You can double that adding a second MSM-48c.
Does it mean the max throughput is 24 * nb_slots? Yes and no. It depends on the traffic pattern and how many L3 entries are considered.
- What about the traffic pattern? I/O module can perform local forwarding, so if your destination is on the same chip, the backplane is not used. Worst case would be every single packet has to go through the backplane.
- What about L3 tables? Simplifying a bit, I/O modules store all the forwarding information in their chip. As long as you stay within their HW capacity, traffic is HW forwarded. But if you put too many entries (too many LPM routes, too many ARP entries, Multicast...) then the chip will not be able to HW forward everything, and the CPU will be used.
You can issue that CLI command to have a view of your L3 resources usage. It's better to execute it during a normal day with a normal activity:
sh iproute reserved-entries statistics
Your limits is listed on the same table of the DS, and this output will also give you the limits. It could be useful to know what EXOS version you're using.
So, assuming you're within the HW capacity, your worst case throughput is 24*5 (slots used) = 120Gbps (or 240Gbps in Marketing math).