You have been granted access to this page through First Click Free. Subsequent use of TabbFORUM will require logging in. If you don't have an account, registration is free.

Videos

  • Rail_thumb_pierre

    The New Risk Transparency Toolbox

    Traditional asset managers are facing an increasingly urgent need to generate alpha, driving a push into alternative investments, from hedge funds to private equity. But as traditional...
     
  • Rail_thumb_adam_honore_david_etue-finqloud-safenet-cloud_security_in_financial_services

    Debunking the Cloud Security Myth

    The idea that the cloud is not secure is a misperception, says David Etue, SafeNet. While the cost and agility gains that come with moving to the cloud also come with a loss of some...
     
  • Rail_thumb_will_rhode-sefszeroesorheroes

    SEFs: Zeroes, or Heroes?

    Swap execution facilities will trumpet a new era of electronic trading in swaps, driving down ticket sizes and commissions and pushing standardization, reports TABB Group director...
     
 

More Video | Podcasts

Advertisement
Original_broadridge_300x250_multi-asset
Original_300x250
Original_original_300x250_12493_0

29 July 2010

Let's Take a "Bit Time" to Talk About Low Latency

Illmer examines the factors that dictate whether faster transmission speed and a shorter "Bit Time" are best for low latency networks.

Talking to customers who are interested in lowest latency solutions, the term "Bit Time" comes up over and over again. But it is not clear what it actually means in terms of low latency and whether a lower "Bit Time" is always better than a higher one. So let's try to explore the background and the implications here.

In general, "Bit Time" stands for the time it takes to transmit a bit for a given network data rate. At Gigabit Ethernet (=1Gbps data rate) the "Bit Time" is 1/(1Gbps) = 1/109 = 1 nanosecond. In other words it takes 1 nanosecond to transmit a bit at 1Gbps. For higher data rates like 10GE the "Bit Time" is even shorter with just 0.1 nanoseconds = 100 picoseconds. But make no mistake - this does not say anything about the actual speed of the signal - it only indicates how many bits can be transmitted during a given second. The speed at which those bits travel over a fiber link is still subject to the maximum speed of light in a fiber, which is approximately 200,000 km/s.

So let's assume we would start a race between a GbE NIC (Network Interface Card) and a 10GbE NIC over a given fiber link. The first bit of the signal would leave both NICs at the very same time. But since the "Bit Time" with 10GE is shorter, the end of the corresponding bit would leave the 10GE NIC earlier than it would leave the GbE NIC. One could also think of it like the bit occupying a certain length on the transmission link. While the bit out of the 10GE NIC only occupies 2 cm, the bit out of the GbE NIC occupies 20 cm, but still their speed on the fiber is the same. So finally they arrive at the end of the link at the very same time. But while the 10GE link has already received the bit completely the GbE link is still waiting for the tail of its bit to arrive. In general the 10GE link has an advantage of 18 cm (20 cm - 2 cm) for each bit received, which translates into a time advantage of 9 picoseconds.

One would think that 9 picoseconds is not much, but unfortunately a normal message does not consist of one bit only and it is embedded inside an Ethernet frame. Normally each frame has to be received (including the CRC) in order to start the processing and forwarding. This, together with the protocol overhead, creates a delay consisting of all the bits and the overhead that make a frame. For the minimum Ethernet payload size of 64 bytes to which a protocol overhead of 22 bytes is added, this translates into a time difference of 620 nanoseconds. This value can go up to 11 microseconds for a frame carrying the maximum Ethernet payload size of 1500 bytes.

So, are a faster transmission speed and a shorter "Bit Time" the better options when it comes to implementing low latency networks? It depends on several factors:

   1. Processing data rates before and after the transport equipment

It does not help a lot if the transmission speed is faster than the actual speed of the client interface that feeds the link or that receives the data. It is always the slowest element in the system that determines the overall processing speed.


   2. Amount of data

If the average message that is sent over to the other side is not very large and can easily fit into a minimum sized Ethernet frame, the gain of going to higher data rates is not so big. On the other hand the advantage gets bigger as the amount of data that needs to be transported increases.


   3. Distance to be bridged

Higher data rates are easier subject to noise and signal distortion. The longer the transmission distance, the worse the distortion problem. In order to bridge higher distances one would have to implement error correction schemes like FEC that always introduce additional latency due to their recursive working principle. A normal FEC for 10GE would introduce up to 30 microseconds of latency, something that would completely eliminate the gain of going to higher data rates.

The best compromise today seems to be the usage of 10GE data rates. 10GE is a common interface with most servers and switches today, and without FEC one could still achieve reasonable distances by using regenerator sites, which would allow to even connect sites that are several 100km apart from each other. For 100GE though, this approach will definitely not work. But that's a topic for another post. Stay tuned …

Comments | Post a Comment

3 Comments to "Let's Take a "Bit Time" to Talk About Low Latency":
  • Missing
    jbiesi

    29 July 2010

    Christian, I think you did a great job of breaking down the numbers and enumerating the key points for decision making when considering the leap to 10 GbE. I think it is important to expand on the first factor because customers need to know how their market centers work. First is is critical to know if information is treated in a pro-rata or time-price-priority fashion and what implications that has whether they are acting a customer (sending orders) or a market maker (sending quotes). Secondly, it is important to have a profile of the exchange and it's systems to judge how quickly they match trades and what risks that poses while orders are live. Much of the low latency business is driven by the equities markets, but as more and more people discover deriviates (futures and options) markets things get really interesting in the choices they can make. Or perhaps this would be an interesting topic for another series... Thanks, -John B Victory Networks

  • Missing
    datacenterstocks

    02 August 2010

    You can get down to about 400 nanoseconds on 10GBASE-CX4, but can go even lower with QDR InfiniBand. With 10GigE Server NICs dropping in price, I'm seeing a lot less debate over GigE vs. 10GigE and more 10GigE vs. 40G InfiniBand.

  • Missing
    tquinn

    03 August 2010

    Interesting article, and the the trend for best platform, for ultra low latency, is a combination of Adva gear, and the Anova Technologies routes(NY/NJ metro), called OptiWave. The Adva equipment can allow for Layer 1 transmission end-to-end(CHI-NJ metro sites), eliminating serial delay. In the metro, only 3 nanos per side is added for each lit circuit. Anova is the only provider that offers these efficiencies, and the mission is to maximize tradde execution performance. For more detail, email tquinn@anova-tech.com.

You must log in to comment.