Why is IB's time 5 seconds behind the official time?

Quote from GTS:

I do not believe that IB-caused delay is impossible, even with their aggregated quotes. Server-side issues can always occur during unusual periods. Further as I previously mentioned network delay is still a possibility that needs to be accounted for.

If you are talking about hardware, that's a different discussion.
I am talking about data structure. When IB is sending 3~4 aggregated quotes per second, that rate is constant, regardless of market volatility.
Compared to a tick-based data feed, when market becomes more active, the data stream can get overloaded because there are more ticks to be sent. (there is no need to discuss this phenomenon, it has been dissected to death here on ET and else where.)
Your computer can be a source of delay too, because it has to process ticks individually.

I don't follow - why couldn't IB include a timestamp that indicates the start or end of the aggregation period?

Theoretically it can be done. But practically you are opening a new can of worm.
 
Quote from Big Game Hunter:

Good idea. If you check esignals website youll see that IB is designed to exactly synvchronise with Esignal tick for tick . MEANING... they support a generic standard for time that THEY share but that they wont allow you to share. Check and see if you dont believe me. REDIPLUS and IB are two platforms which allow for whats known as 'integrated trading' meaning they both synchronise THEYRE clock with each other precisely.
I'm completely with you on this. I had a post on the Ninja forum asking for RELIABLE NTP servers. Every server I've tried has been off by a few seconds....and I "sync" every hour.
What do I have to do to get Win/XP to tell me the correct time ?
It's totally amazing that in this day and age, computers can't tell the right time down to the second.
WAIT ! I just checked and today, at this moment, I'm spot on !
FINALLY !!!!
 
The API derives time from the server time (same time that is displayed on the lower right corner of TWS), not the PC clock.


Quote from GTS:

If that is the case and IB's API does not timestamp data then *that* should be the complaint.

The end-user should not be assuming the timestamp of incoming data based on their local clock - the timestamp should be included in the data format.

If IB doesn't timestamp their data then that just reflects badly on their API.
 
If IB doesn't timestamp their data then that just reflects badly on their API.
or the fact that like me, they cannot find any reliable NTP servers as well.
Today, I'm off a whopping 30 seconds. Some days I'm "spot on".
My current server is:
2.us.pool.ntp.org

Someone on the NinjaTrader forums suggested the real problem lies with Microsoft's W32TIME api...which is the one that controls the updates from the NTP server.
I'm starting to believe this now.
I'm supposed to get updates every HOUR, but I don't think this is happening.
IN FACT, I AM RIGHT ON THIS...HERE IS THE MESSAGE FROM MY EVENTS LOG:
The time service is now synchronizing the system time with the time source 2.us.pool.ntp.org (ntp.m|0x1|192.168.1.6:123->131.128.183.247:123).

This occurred at 9:30 this morning.....in fact it (the update)happened twice....SO THAT'S A BUG. Also, the update at 10:30 NEVER HAPPENED. Another bug.

Conclusion: Windows/XP cannot tell time.
Wow. Scary if traders are relying upon it.
 
I am using time.nist.gov.

You can change the polling interval to be more frequent too:

http://support.activehost.com/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=300

5. Select the poll interval. To do this, follow these steps:

a. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimeProviders\NtpClient\SpecialPollInterval

b. In the right pane, right-click SpecialPollInterval, and then click Modify.

c. In Edit DWORD Value, type TimeInSeconds in the Value data box, and then click OK.

Note TimeInSeconds is a placeholder for the number of seconds that you want between each poll. A recommended value is 900 Decimal. This value configures the Time Server to poll every 15 minutes.
 
Quote from Big Game Hunter:

The clocks on IB's time servers are 5 seconds slower than the official us time shown here...

http://www.time.gov/timezone.cgi?Eastern/d/-5/java


Given how absolutely crucial timing is in this trading game can anybody else smell a big rat too? I am so pissed of about this. Its really really underhand. What I want to know is why as I was typing this the clocks went back to being the same. I just went back to check again as I was typing and now they are the same. For every layperson out there who uses I.B I suggest you check that the internal IB clock exactly matches the official US time clock since I am 100 % positive that mine was operating with a 5 second lag. There are some serious implications to this kind of time manipulation and its best you get to grips with them. This kind of manipulation is borderline criminal and Im not going to sit back and ignore it. It fucks all the timing up with my figures.

Could there be a conspiracy between the market-makers and the Time Lords?
 
It is exceedingly difficult to synchronize your computer to any standard via the internet. Using a program such as D4 (http://thinkman.com/dimension4/index.htm) you can get a time sync from any of the world standards available via the internet. However, the length of time between the transmission of the sync info and its receipt by your computer is a variable based on internet routing and internet loading. This latency is not a constant. Further, IB aggregates and samples the quotes you receive. You are not getting an exchange provided feed, that is one of the reasons IB does not have to charge exchange fees for its data feed, you are not getting a bit-by-bit retransmission of exchange data.

If you run TWS you've probably seen the time in the lower right corner of the TWS. As an experiment set your computer clock to an hour or two away from the correct time and then start TWS. Then shutdown TWS, reset the computer time to an internet-synced time standard and restart TWS.

If you use D4 (or some other similar utility) the time difference between the timestamp you apply to the IB datastream and the actual time IB receives data from the exchanges and ECNs should be within 200 to 400 milliseconds depending on:
The latency of the internet sync signal
The latency of the quote stream from the exchange to IB
IB's 100-300 millisecond processing delay
The latency between your machine and the IB server.

IB could time stamp its data but why should they? As a trader, even a fully automated trader, it should make no difference to you. The only reason I could think of for needing to know the actual time was so that I could compare the quote (or tick) time against my machine time. If I detected a significant deviation between the normal latency and the current latency I could stop trading if my system would be affected by such a change.

I don't know for sure, but I believe IB's API does have a function that allows a call to the IB clock. You could use such a call to monitor latency variations, if it mattered.

Jack
 
Quote from Big Game Hunter:

The clocks on IB's time servers are 5 seconds slower than the official us time shown here...

http://www.time.gov/timezone.cgi?Eastern/d/-5/java


Given how absolutely crucial timing is in this trading game can anybody else smell a big rat too? I am so pissed of about this.

Told you, IB is using watches made in China. When I buy a watch, I look for two small words on the watch: Japan Movement.
 
Back
Top