does 6.1 throttle data?

[btrluckythngood]

Can anyone confirm that QC 6.1 does not throttle data like QC 5?

The reason I'm asking is that I get streaming quotes from three different brokers. There are frequent times (not all of the time) when prices will move simultaneously with the brokers and is not reflected with QC until a few seconds later. The delay time varies, but is noticable.

Windows task manager does not show the CPU nor memory to be overtasked by any means.

Has anyone else noticed this?

[ckelly]

Re: does 6.1 throttle data?

Originally posted by btrluckythngood
Can anyone confirm that QC 6.1 does not throttle data like QC 5?

The reason I'm asking is that I get streaming quotes from three different brokers. There are frequent times (not all of the time) when prices will move simultaneously with the brokers and is not reflected with QC until a few seconds later. The delay time varies, but is noticable.

Windows task manager does not show the CPU nor memory to be overtasked by any means.

Has anyone else noticed this?

Lucky,
I see this on a regular basis, and lately, just about every day. Today, my QCharts candles were typically 30-60 seconds behind my broker (IB).

I've gotten used to it - the bigger issue for me is when the price painted differs from time frame to time frame. See here

fyi,
Carol

[btrluckythngood]

Jay,

Could you or someone from esignal confirm whether or not qc6 is throttling ticks like qc5?

Thanks,
better lucky than good

[JayF]

btrluckythngood,

We are not throttling data. The delays that have been seen at times are the result of server issues that we are very actively working through. In fact, today this issue should no longer be seen.

[btrluckythngood]

I'm seeing the delay issues again today, and it's multi-seconds across multiple tickers. I'll see prices change on multiple broker feeds, and the the prices just "hang" on qc.

If this is a server issue, it it across all servers or limited to particular servers? The reason I'm asking is to find out if I can select servers that may not be affected, or where the issue is minimized.

This is an issue that affects my trading, particularly using one minute charts. ANY insight from anyone from esignal or any users would be much appreciated.

Thanks,
better lucky than good

[eSignal_ToddI]

There was a server upgrade last night that affected access to versions of QCharts older than the most recent 6.1 (1757).

Currently those servers that were upgraded last night are offline, which has resulted in the current data lags.

Engineering/Operations are looking into this issue currently.

[tradertom]

I saw that happening this morning on NQ futures as the market was falling fast just after the open. It was a bit frustrating to watch the option bid/asks moving on my brokers' feeds while the charts were seemingly stuck.

I just chalked it up to higher volume trading swamping the servers as the NASDAQ was getting pounded down in the first 20 minutes of the day. It was not the first time it has happened since v6.1 but it happened all the time with 5.1 so while it is improved, it would be sure nice to have it fixed for such days. I just don't think volume should affect the feed in this way.

Todd, Thanks for the update. Redundant systems on the server side would prevent such lags in data. I am not sure why eSignal and QCharts users should even notice any such maintenance issues.

[btrluckythngood]

Thanks, Tom and Todd for your replies. While I am not seeing the delays now (maybe because prices aren't moving as fast as this morning?), they were there even around 1100 EST. I am running 1757.

I agree with Tom that this is very frustrating, particularly when entry/exit decisions are affected and it feels like you're leaving money on the table. Are there any solutions out there that don't leave us at the mercy of server issues?

Thanks again,
better lucky than good

[eSignal_ToddI]

Engineering has brought online more of the upgraded Data Managers which should help with the lagging data issues.

The upgrades are necessary but have a conflict when older versions of QCharts launch and try to connect to them so it's imperative for clients to be running version 6.1 (1757) as soon as possible.

Once QCharts clients are upgraded to the current build, engineering will be able to expand the servers QCharts can connect to on the eSignal network as most of those DMs have already been upgraded.

[dcash]

I am watching an online presentation right now coming out of the Las Vegas money show. The presenter has the ES 2 min chart up on eSignal Pro. I have the same chart open in QCharts (Richmond, VA). His chart is updating anywhere from 5 to 10 seconds sooner than mine.

Why is eSignal updating sooner than QCharts? Don't we access the same servers? He is physically closer to the server farm, but not 5-10 seconds worth.

[eSignal_ToddI]

To elaborate on my previous post.

Most of the eSignal network runs a version of Data Manager (DM) that causes connection problems with older versions of QCharts, even QCharts 6.1 (1719).

The current version of QCharts is 6.1 (1757) which can handle the current DM version (server side version, not the one on the client's desktop).

As a result of this, QCharts clients had to be routed to a subset of DMs that were on not upgraded.

Those DMs are in the process of being upgraded but due to the number of clients that need to go to the current build, those upgrades have been slower than if clients did not have such access problems with older versions of QCharts.

Once all the DMs that QCharts clients connect to are upgraded, then they won't have to be routed to this subset of DMs and the clients will have many more servers that can share the workload and consequently reduce the lagging issues as well as offer much more redundancy.

Wednesday night a group of DMs were upgraded and resulted in a spike in calls due to access problems with QCharts. Consequently all of the new DMs were initially taken offlne. Many of those new DMs are in the mix today, but QCharts still has fewer servers currently online than there were earlier this week. Monday there should be more upgraded DMs in the rotation and again once they're all upgraded, then access to the DMs available will be open.

[btrluckythngood]

noticeable lag in data

Seeing a noticeable delay in data today. On occasion seeing a two cent difference between qc and multiple broker feeds. Anything I can do to eliminate/minimize the discrepancy?

Thanks,
betterluckythangood

[billbled]

Hey
Specifically, what ticker(s) are you seeing delayed. It may be related to your subscriptions.

[btrluckythngood]

Thanks, Bill for the response. Multiple Nasdaq listed stocks. Haven't looked at other exchanges nor options.

Thanks.

[ckelly]

Bill,
Same thing here today, on various stocks like AAPL, GOOG, AMZN, for example. Several times, AMZN was 75 seconds idle (based on not-painted 1-min candles) and also the TT (time of trade) in the Snapshot Window. It was especially noticeable as AMZN did 2.3X avg volume today.

During those idle times, my broker and another charting service were updating - and at many times QC prices were 0.5-0.75 different from my Broker.

FWIW, yes, I did a computer & QC reboot a couple of times trying to get to another server - the throttling continued all day.

fyi,
Carol