Live data from Hacker News

Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

nytimes.com

71–80 of 143 posts

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#71
post #53

Earlier quoted context omitted.

I maintain an NTP implementation. That comparison doesn't seem fair to me. It looks like they are comparing the old reference NTP implementation and not really the protocol itself. An NTP implementation can certainly synchronize clocks with better accuracy than 1 millisecond, or even 1 microsecond with hardware timestamping and good network switches. There are some interesting ideas in the Huygens paper, but I don't…

The other thing I don't understand is that this paper argues against hardware timestamping on the grounds that users won't want to buy expensive hardware, and that Huygens is for "standard hardware ... in current data centers". Expensive, niche hardware is normal for the HFT folks that care about nanosecond precision.

The paper did not have hft as its primary use case, but you cannot contain reporters tendency to cherry pick eye catching aspects.

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#72
post #53

Earlier quoted context omitted.

I maintain an NTP implementation. That comparison doesn't seem fair to me. It looks like they are comparing the old reference NTP implementation and not really the protocol itself. An NTP implementation can certainly synchronize clocks with better accuracy than 1 millisecond, or even 1 microsecond with hardware timestamping and good network switches. There are some interesting ideas in the Huygens paper, but I don't…

The other thing I don't understand is that this paper argues against hardware timestamping on the grounds that users won't want to buy expensive hardware, and that Huygens is for "standard hardware ... in current data centers". Expensive, niche hardware is normal for the HFT folks that care about nanosecond precision.

Good support for PTP in network switches is rare. If the users don't want to spend a lot of money on new switches with PTP support, they can synchronize clocks in the network with a protocol which doesn't require special support in switches.

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#73
post #13

Earlier quoted context omitted.

Why would you use floating point math for finance?

A floating point representation is not really the issue, the issue is not using base 10, and IEEE 754 specifies base 2 and base 10 floating point formats and operations. But I am of course not sure whether the original comment referred to base 2 or base 10 and given how common the mistake of using base 2 floating point numbers for financial calculations is, you may be correct with the intention of your comment.

I'm aware of the fact that you don't use floating point math for finance -- for exactly the reason you described -- but the academic in me wonders if you could formally specify a high-enough degree of precision -- and all the corner cases -- to allow FP math for even just a subset of transactions. This would (in theory) allow to programmers to bypass the Decimal classes in your favorite OO language (or GMP if you're a C fan).

Again, purely an academic inquiry :-)

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#74
post #20

"So-called high frequency trading firms place trades in a fraction of a second, sometimes in a bet that they can move faster than bigger competitors." First off: no. Big money plays in high frequency trading (roughly half of all trading activity), and the smaller traders without instantaneous access are the losers in this game. Secondly, NASDAQ's obsession with precise global sequencing is A) misguided and B) effecti…

I'm a slow trader -- a few trades a year. I like, or at least don't mind, HFT.

It certainly doesn't hurt liquidity. There is, in principle, always someone who wants to trade with me, and the increased volume may make price-discovery a little more accurate.

When I place a limit order, I don't mind at all if someone has managed to front-run my order and sell it to me at the price I set. I got the thing I wanted to buy at the price I wanted to pay.

HFT is only troublesome if you play with fire -- market orders. The price you see may not be the price you get with a market order, as the market can do irrational things or front-run you. That risk is blunted entirely by limit orders. Your order might not fill, but when it does fill, it will only fill at or better than the price you asked.

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#75

Earlier quoted context omitted.

"Also, no, small traders don't lose. Retail traders et al get much tighter spreads, cheaper execution by routing to internalizers, etc." There's liquidity until there isn't. It was easier to get an order filled during a run to the exit pre-HFT. When everyone runs to the exit in an HFT world, retail investors are the last to get their orders filled, if they're lucky.

Manning rule dictates that retail orders held by a market maker must be filled before any other orders (or equally that fills must be given to the retail order), brokers don't look kindly on firms that reject customer orders with any regularity, and anyways retail flow on a volatile+wide spread symbol are loved by market makers.

This. Even in markets with last look, you will lose your flow if you dick about too much.

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#76
post #61

Earlier quoted context omitted.

Most HFT shops are relatively small. HFT is all about latency and turn over. Big quant shops might have HFT elements but lean far more towards systematic/algo strategies that can be relatively high latency (still super low latency, but not HFT) because these are the only strategies that you can deploy serious var with. The guys crushing HFT are not huge hedge funds, and they are solving more engineering problems than…

Of course the retail guy gets hurt. Who do you think buys the mutual funds that pay a higher price. Seriously, I hear this all the time, but it’s only one step removed. Why does everybody keep repeating this lie?

Yes, this is indeed true. Not sure why you're being downvoted. The distinction is still one worth making, because average retail investors can typically have better transparency on this in a mutual fund vis-a-vis tracking error and management fees, whereas a retail trader in the open market is going to have almost no idea where the market really was for that market order they dumped into their Etrade account.

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#77
post #61

Earlier quoted context omitted.

Of course the retail guy gets hurt. Who do you think buys the mutual funds that pay a higher price. Seriously, I hear this all the time, but it’s only one step removed. Why does everybody keep repeating this lie?

Vanguard states that hft activities have lowered their trading costs, so I don't think this claim is necesarily true.

HFT has reduced costs under 99.99% of market environments. My direct cost and slippage is still so much lower than it would have been 30 years ago. Hell, even 10 years ago.

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#78
post #63

Earlier quoted context omitted.

I don't know if this is true, but higher liquidity and lower spreads reduces the cost of every trade, which is money in the pockets of retail and value investors. I assume this is why Vanguard says HFT has been helpful for them (despite the fact that they don't do HFT themselves).

Aren't the cost of the trade and price of the trade two different things? Tighter spreads can only do so much to offset disadvantageous pricing, right?

What difference are you making between tighter spreads and disadvantageous pricing?

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#79

Earlier quoted context omitted.

Most HFT shops are relatively small. HFT is all about latency and turn over. Big quant shops might have HFT elements but lean far more towards systematic/algo strategies that can be relatively high latency (still super low latency, but not HFT) because these are the only strategies that you can deploy serious var with. The guys crushing HFT are not huge hedge funds, and they are solving more engineering problems than…

"Also, no, small traders don't lose. Retail traders et al get much tighter spreads, cheaper execution by routing to internalizers, etc." There's liquidity until there isn't. It was easier to get an order filled during a run to the exit pre-HFT. When everyone runs to the exit in an HFT world, retail investors are the last to get their orders filled, if they're lucky.

Yeah and the old DMM's used to stub quote when things got rough. Same shit, different day. Under most environments, HFT has been a net positive particularly in the single name options market. Pretty much every name out there is quoted with decent depth because an algo can now quote a few vols either side and make decent coin given that it costs nothing to stay laid up these days.

Re: Google and Nasdaq Pursuing Nano-Second Precision in Network Time Protocol

#80
post #38
post #37

Earlier quoted context omitted.

why should randomization be clever? just fulfill orders in the book randomly for each time interval, wouldn't that be enough?

If I place an order to buy 1 share for $1 and another share for $1.01 because the market data shows that there is only one share available for $1, then the exchange needs to process my $1 order before my $1.01 order. More complicated scenarios exist, too, especially once you take into account resting orders and modifications to existing resting orders.

Right, unless exchange explicitly documents the fact that order of fulfillment is not guaranteed if you place them within the same time interval.
Post reply on HN