It has been an old grievance of mine, because I remember the good ol’ days of C2, when a market order went through immediatelly, but not slower than 2 seconds. Today I had 2 positions when I was up nicely so I push the Place order and I counted the seconds and I got it filled 20 or more seconds later with the new, 20 seconds newer price. I understand that C2 is not for scalpers, but come on!
I suggested this earlier that all the statistical computation should be suspended during RTH or done only once an hour, because I bet that’s what is slowing the system down.
C2 started to remind me of Vista, all the new shiny bells and whistles but with the unfortunate slowdown…
Actually I am working on some improvements for system responsiveness during peak hours. If my recent software development and infrastructure changes work as expected, these delays will become increasingly rare. Let’s see how the next few days go, please.
MK: maybe it was my connection, but near the close did things get a bit congested?
gA
Yes. Volume everywhere is nuts, and I’m working on handling it more gracefully.
Today it is impossible to trade. I am getting completely bogus fills, it is like a casino. The price is/was nowhere near what C2 shows. I tried limit orders too, one should have been filled 5 minutes ago with a nice gain (price went through by a whole point) and it is still sitting there as it was a loss…
Very frustrating. I don’t even complain anymore about 2 points slippage but today I had 6 points in one trade!!!
Welcome to the world of being completely annoyed and fed up with the fills and slippage. Impossible to trade. Should be no excuse for it today as there is no volatility in the mkt. Soon it will be time for me to pay my 6 month fee again. I will be thinking hard about it.
I totally understand your frustration and am working hard behind the scenes to address these problems.
For now, please fill out trouble tickets. I promise I am working on making the quote feeds more accurate and responsive.
Is this affecting autotrade fills? Or just how the fills are reported in the stats?
No. It is affecting only the on-screen reports of fills shown via C2’s Web interface.
FWIW, I just turned on some new code which ought to speed up on-screen fill-reporting for market orders.
how do i complete a trouble ticket?
From the main trading system page make sure that "Report Problem" Links is turned on …
Then click the trade from the performance report where the data may be in error to request a review.
I am sorry to report that C2 is still too slow today. There was only one late/bad fill, but I didn’t get a confirmation of the trades up to a minute or more, and I was wondering if I was in a position or not…
I agree. Unacceptable performance. But, I’ve done some investigating, and I am getting to the bottom of this. It appears one or two users are simply swamping the site with hundreds and hundreds of orders simultaneously. This is nobody’s fault, and I am not blaming anyone. It is C2’s responsibility to make sure the site stays responsive for everyone.
I am adding some throttling logic now.
throttling logic?!?
Heh-heh, yeah. . .that’s it, sounds GOOD.gA
Matt -
Perhaps you can add some "throttling logic" to the forums…
Beside not running statistics during RTH, I have another idea:
What about having 2 different servers and the top 50 or so systems with PAYING costumers would get the faster server? I know it doesn’t sound fair, but those are the ones having real money at stake, so they could get prefered treatment. Of course general fast fills would be the best, but until we can get that, we take whatever we can…
"It appears one or two users are simply swamping the site with hundreds and hundreds of orders simultaneously."
Ahh… that sounds familiar. I once subscribed to SMS alerts to a service like that, and found myself receiving over a hundred text messages a day, in bursts. Yes… throttle away, please!
Maybe freeze the account of the worst offenders.
If someone is dumping a large amount of traffic, they may be costing you more $$$ than you get from them in revenue…
Just an fyi… it seems to have abated somewhat. Thanks again Matthew for working on this issue.
