Fiber cables made of air move data at 99.7 percent the speed of light
arstechnica.com
arstechnica.com
[1] http://www.forbes.com/forbes/2010/0927/outfront-netscape-jim...
http://www.extremetech.com/extreme/122989-1-5-billion-the-co...
Failures can cause exchange crashes big time. This has nearly happened a few times before.
Risk is centralised and multiplied.
HFT contributes to volatility.
Hurts long term investment by human brokers.
- Can't failures be counteracted by having failsafe measures? For example, if the market goes down more than 5% in a few-minute period, the market temporarily shuts down for a cooloff period of several hours to diagnose what's happening.
- Isn't HFT irrelevant to long term investment, given that it erodes away short-term profit, leading to accurate pricing of the stock?
A failsafe/circuit breaker is a possibility but shutting down the market will affect confidence. I'd prefer to see a market operate on a tick basis I.e all trades for a tick are transacted in one go with a window between each tick and assertions before and after the tick processing.
Fair point with your second comment.
If by "all but eliminating" they mean "reducing by 31%".
There's a hard limit to how low latency can go. We've been close to it for years. So a hop takes 100 ms instead of 150 ms? They're still in the same ballpark. To have a revolutionary impact, it would have to drop the latency an order of magnitude, which, as far as we understand our universe, is impossible.
I guess the real application is over short distances. I'd love to hear the ideal usecase that benefits from this improvement.
At only 37 channels, compared to the 80 that more traditional fiber can carry using DWDM, it also carries less than half the capacity. And that's assuming that it's capable of the same bandwidth capacity per channel; the article states 40Gbps per channel, whereas you can already go as high as 100Gbps over a single wave using DWDM, which means it may only be able to carry 18.5% as much.
Lets say your application needs <50ms latency, low enough that your users can't notice. Today, you'll something around 10 datacenters in the USA/Canada to achieve this.
If cut that down by 31%, you might only need 6. (or less, this would take some real math to figure out).
But the impact is pretty large in the long run, if it can really cut long haul latencies by 31%.
Still not the case. The state-of-the-art networking technologies are expensive (300K+/yr per data center plus inter-facility connectivity running into the 1-5M/yr range)
If you think about a recording studio experience, you usually lay down a rough basic track and overdub on top of it. In that case, latency doesn't really matter as much as good tools for collaboration and iteration.
These systems are designed to either induce constant latency (TDM, one frame period per switch) or induce lowest possible latency (SoNET/SDH with very clever mechanism to construct frames without knowing their full content and decoding them incrementally, which gives best case latency of few bit times + latency of any fiber interface, worst case comparable with traditional TDM).
The problem with latency and telephony is two fold: echo cancellation for single pair analog phones (phone itself only substracts outgoing signal from incoming so anything that is echoed from other side of line goes through) and maximal latency for comfortable conversation (which is surprisingly small). First problem can be solved with smarter interfaces that do echo-cancellation in some DSP (some kind of license for doing that is major part of cost of analog interface cards for open source PC based softswitches), second not so much.
So in all you can reasonably jam remotely (on distances of say less than 2000km) using this infrastructure and using it is probably few orders of magnitude cheaper (renting channels in SDH/SoNET optical networks is actually surprisingly cheap) than laying special fibres.