21–30 of 83 posts
Earlier quoted context omitted.
I feel like it's also got to be super stressful Imagine getting a call you system is down and is costing them millions per hour
I'd want to know why they had such a system as a single point of failure
less than 60ns loopback latency There are some Ethernet switches with 4ns latency, and those do more than just sending and receiving, so there's clearly still an order of magnitude of improvement still available. 4ns is basically ~40 cycles of the bit clock for 10G Ethernet.
It seems fun to be a high frequency FPGA trader designer. All my FPGA is much lower power consumption so I don't get to play with stuff like gigs of external SRAM or the QDR stuff or whatnot
I feel like it's also got to be super stressful Imagine getting a call you system is down and is costing them millions per hour
Earlier quoted context omitted.
Cut Through switching needs what, 14 bytes? Thats ~12ns on 10G? How would you do it in 40 cycles?
why do you assume the full ethernet header? IIRC. cut-through only needs the first 6 bytes. Since it only needs the destination address for the port lookup. Potentially the first bit, on broadcast.
Earlier quoted context omitted.
I feel like it's also got to be super stressful Imagine getting a call you system is down and is costing them millions per hour
The way to think is the opposite: your system is making millions per hour.
Earlier quoted context omitted.
I feel like it's also got to be super stressful Imagine getting a call you system is down and is costing them millions per hour
I'd want to know why they had such a system as a single point of failure
Earlier quoted context omitted.
I feel like it's also got to be super stressful Imagine getting a call you system is down and is costing them millions per hour
The way to think is the opposite: your system is making millions per hour.
Earlier quoted context omitted.
The way to think is the opposite: your system is making millions per hour.
What about when something goes wrong because you overlooked some detail?
less than 60ns loopback latency There are some Ethernet switches with 4ns latency, and those do more than just sending and receiving, so there's clearly still an order of magnitude of improvement still available. 4ns is basically ~40 cycles of the bit clock for 10G Ethernet.
Essentially a few ns after the header is received it will already be passed on to the output port after some signal conditioning, which happens almost without latency. A typical 'high speed' switch will have 800 ns round trip, so that 60 ns quoted here is actually quite impressive.