Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sat, 20 Apr 2024 13:43:25 +0000
AMP Rithmic service data
View Count: 4242
| [2014-03-13 12:57:31] |
| Carl71 - Posts: 125 |
|
Do they provide backfill data tick by tick? It seems they don't How can I get tick by tick data? Thanks from your website: "...Sierra Chart fully supports the Rithmic trading platform service. Rithmic provides low latency trading and market data. With this trading and data service you have access to real-time data, historical data and trading in the futures, stock and currency markets from many exchanges around the world. The Sierra Chart trading features fully support the Rithmic trading platform service. You are able to enter simple and advanced orders from the charts, ChartDOM, Trading DOM and Trade Window all within Sierra Chart. Rithmic is an excellent backend trading platform service providing tick by tick data and reliable trading services." Date Time Of Last Edit: 2014-03-13 13:05:38
|
 Rithmic Number Bars.png / V - Attached On 2014-03-13 13:02:53 UTC - Size: 54.82 KB - 1138 views |
| [2014-03-13 13:54:21] |
| Carl71 - Posts: 125 |
|
Another question I noticed Rithmic shows a price lag compared to CQG (about 1 second) under fast market condition SC Chart update interval set to: 10 ms My ping to Chicago is 130 ms, packet loss 0, jitter 2 I tried via Task manager to set priority "real time" both DTCBridge and Sierra Chart It seems things are better. Now CQG is always slightly behind Rithmic Do you think that Task manager priority may influence real time data? Your advice is to set both process "real time"? I have Win7 Thanks Date Time Of Last Edit: 2014-03-13 14:15:47
|
| [2014-03-13 16:37:02] |
| |
|
When using Rithmic you will not get historical tick by tick data. You will need to use the Sierra Chart market data feed for this: https://www.sierrachart.com/index.php?l=doc/SierraChartRealTimeFuturesStockDataFeed.php We do not recommend you to set a Chart Update Interval this low: SC Chart update interval set to: 10 ms We cannot comment on the process priority. You have to make your own determinations on those things. That's outside the scope of our support. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2014-03-13 19:54:05] |
| Carl71 - Posts: 125 |
|
We cannot comment on the process priority. You have to make your own determinations on those things. That's outside the scope of our support.
Yes, all I can say is that: it works I was aware that the delivering of unfiltered ticks may cause problems In this case if you have a low latency like a ping below 150ms, things are fine I also tested the real time priority with a internet wireless connection that brings latency (ping over 350ms) very high. Well...in this case this particular setting didn't work |
| [2014-03-13 20:56:48] |
| |
|
Come to think about it the DTC bridge program that we use with Rithmic could introduce up to something like 100 ms of delay. It was hard to solve this because Rithmic uses a multithreaded API component. Information about API components can be found here: http://www.sierrachart.com/index.php?l=doc/helpdetails76.html We do not use a direct interfacing method , but we wish we could. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-03-13 20:57:19
|
| [2014-03-14 08:03:50] |
| Carl71 - Posts: 125 |
|
I noticed in another thread related to possible lag within Rithmic service, your advice to use the Rithmic 01 Aggregated server I trade from Europe and I see there is a server located in Europe Do you think it's better for me to use Rithmic 01 Europe? Now I am testing Rithmic in paper demo server, so I can't have any opinion about it Ping test to Chicago is 130 ms, in Europe 40ms Can you provide the name server (ip address) of Rithmic Europe? Could you please give me some advice? Date Time Of Last Edit: 2014-03-14 08:05:32
|
| [2014-03-14 08:45:21] |
| |
|
We would definitely recommend using Rithmic 01 Europe, as long as you can get a successful connection. We do not know if there is any special configuration required for your trading account to be done to use that server. Address information for Rithmic Europe as provided by Rithmic to us: ritpz01001.01.rithmic.com:65000~ ritpz01000.01.rithmic.com:65000~ ritpz01001.01.rithmic.net:65000~ ritpz01000.01.rithmic.net:65000~ ritpz01001.01.theomne.net:65000~ ritpz01000.01.theomne.net:65000~ ritpz01001.01.theomne.com:65000~ ritpz01000.01.theomne.com:65000 Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-03-14 21:19:30
|
| [2014-03-14 10:15:18] |
| Carl71 - Posts: 125 |
|
Anyway I've found this thread: Rithmic Europe It's sufficient for me to set Rithmic 01 - Europe to reach the server located in Ireland, or you have to set this up for me? |
| [2014-03-14 15:07:47] |
| Carl71 - Posts: 125 |
|
Strange thing, the addresses you provided now work, but none of them are located in Ireland (Europe) Furthermore the final destination is unreachable Traccia instradamento verso ritpz01000.01.rithmic.com [38.103.114.53] su un massimo di 30 punti di passaggio: 1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1] 2 * * * Richiesta scaduta. 3 6 ms 6 ms 6 ms 151.6.48.4 4 7 ms 6 ms 6 ms 151.6.48.152 5 16 ms 10 ms 11 ms MICA-TO2-GECA-B01-po01.wind.it [151.6.6.13] 6 12 ms 13 ms 12 ms 151.6.2.182 7 20 ms 17 ms 17 ms Vlan525.icore1.WI3-Milan.as6453.net [195.219.166 .13] 8 13 ms 12 ms 13 ms if-1-0-0-96.core3.MLT-Milan.as6453.net [195.219. 158.29] 9 119 ms 118 ms 151 ms if-7-0-2-0.tcore1.PVU-Paris.as6453.net [80.231.1 53.45] 10 119 ms 119 ms 119 ms if-2-2.tcore1.PYE-Paris.as6453.net [80.231.154.1 8] 11 118 ms 123 ms 123 ms if-3-6.tcore1.L78-London.as6453.net [80.231.130. 85] 12 155 ms 129 ms 152 ms if-4-2.tcore1.NJY-New-Jersey.as6453.net [80.231. 130.34] 13 123 ms 119 ms 119 ms if-2-2.tcore2.NJY-New-Jersey.as6453.net [66.198. 70.2] 14 121 ms 121 ms 120 ms if-14-14.tcore2.NTO-New-York.as6453.net [66.198. 111.126] 15 113 ms 114 ms 113 ms be3011.ccr21.jfk05.atlas.cogentco.com [154.54.12 .17] 16 127 ms 126 ms 126 ms be2060.ccr21.jfk02.atlas.cogentco.com [154.54.31 .9] 17 136 ms 136 ms 136 ms be2114.ccr21.ord01.atlas.cogentco.com [66.28.4.2 02] 18 158 ms 140 ms 141 ms be2005.ccr21.ord03.atlas.cogentco.com [66.28.4.7 4] 19 137 ms 137 ms 138 ms te3-1.mag01.ord03.atlas.cogentco.com [154.54.40. 182] 20 138 ms 137 ms 138 ms 154.24.22.30 21 * * * Richiesta scaduta. 22 * * * Richiesta scaduta. 23 * * * Richiesta scaduta. Traccia instradamento verso ritpz01000.01.rithmic.com [209.130.209.130] su un massimo di 30 punti di passaggio: 1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1] 2 * * * Richiesta scaduta. 3 7 ms 7 ms 6 ms 151.6.48.6 4 7 ms 7 ms 7 ms 151.6.48.154 5 96 ms 10 ms 11 ms 151.6.6.29 6 12 ms 12 ms 12 ms 151.6.2.178 7 22 ms 17 ms 17 ms Vlan525.icore1.WI3-Milan.as6453.net [195.219.166 .13] 8 23 ms 22 ms 22 ms if-8-2125.tcore1.FR0-Frankfurt.as6453.net [195.2 19.50.149] 9 39 ms 39 ms 39 ms 208.178.58.229 10 131 ms 42 ms 42 ms ae-9-0.edge4.Frankfurt1.Level3.net [4.68.63.241] 11 128 ms 128 ms 127 ms vlan80.csw3.Frankfurt1.Level3.net [4.69.154.190] 12 127 ms 125 ms 126 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9] 13 125 ms 125 ms 125 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134] 14 126 ms 126 ms 125 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5 0] 15 125 ms 124 ms 124 ms ae-47-47.ebr2.Washington12.Level3.net [4.69.202. 58] 16 124 ms 125 ms 125 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146] 17 126 ms 125 ms 126 ms ae-203-3603.edge2.Chicago2.Level3.net [4.69.158. 57] 18 * * * Richiesta scaduta. 19 * * * Richiesta scaduta. 20 * * * Richiesta scaduta. Traccia instradamento verso ritpz01000.01.theomne.net [209.130.209.130] su un massimo di 30 punti di passaggio: 1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1] 2 * * * Richiesta scaduta. 3 * 9 ms 6 ms 151.6.48.6 4 12 ms 40 ms 14 ms 151.6.48.154 5 11 ms 11 ms 14 ms 151.6.6.29 6 13 ms 12 ms 12 ms 151.6.2.182 7 13 ms 17 ms 14 ms Vlan525.icore1.WI3-Milan.as6453.net [195.219.166 .13] 8 23 ms 22 ms 22 ms if-8-2125.tcore1.FR0-Frankfurt.as6453.net [195.2 19.50.149] 9 39 ms 39 ms 39 ms 208.178.58.229 10 41 ms 42 ms 42 ms ae-9-0.edge4.Frankfurt1.Level3.net [4.68.63.241] 11 128 ms 127 ms 127 ms vlan80.csw3.Frankfurt1.Level3.net [4.69.154.190] 12 126 ms 125 ms 125 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9] 13 125 ms 124 ms 124 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134] 14 126 ms 126 ms 126 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5 0] 15 124 ms 124 ms 124 ms ae-47-47.ebr2.Washington12.Level3.net [4.69.202. 58] 16 126 ms 125 ms 124 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146] 17 128 ms 125 ms 129 ms ae-203-3603.edge2.Chicago2.Level3.net [4.69.158. 57] 18 * * * Richiesta scaduta. 19 * * * Richiesta scaduta. Traccia instradamento verso ritpz01000.01.theomne.com [209.130.209.130] su un massimo di 30 punti di passaggio: 1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1] 2 * 7 ms * 151.6.140.72 3 6 ms 6 ms 6 ms 151.6.48.6 4 7 ms 9 ms 6 ms 151.6.48.154 5 81 ms 11 ms 10 ms 151.6.6.29 6 12 ms 12 ms 12 ms MIOT-B01-MICA-T02-po01.wind.it [151.6.2.74] 7 24 ms 17 ms 17 ms Vlan525.icore1.WI3-Milan.as6453.net [195.219.166 .13] 8 23 ms 24 ms 22 ms if-8-2125.tcore1.FR0-Frankfurt.as6453.net [195.2 19.50.149] 9 41 ms 39 ms 39 ms 208.178.58.229 10 42 ms 42 ms 42 ms ae-9-0.edge4.Frankfurt1.Level3.net [4.68.63.241] 11 128 ms 127 ms 127 ms vlan80.csw3.Frankfurt1.Level3.net [4.69.154.190] 12 126 ms 125 ms 125 ms ae-81-81.ebr1.Frankfurt1.Level3.net [4.69.140.9] 13 125 ms 126 ms 433 ms ae-45-45.ebr2.Paris1.Level3.net [4.69.143.134] 14 127 ms 127 ms 126 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5 0] 15 124 ms 126 ms 124 ms ae-47-47.ebr2.Washington12.Level3.net [4.69.202. 58] 16 124 ms 125 ms 125 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146] 17 126 ms 126 ms 126 ms ae-203-3603.edge2.Chicago2.Level3.net [4.69.158. 57] 18 * * * Richiesta scaduta. 19 * * * Richiesta scaduta. Date Time Of Last Edit: 2014-03-14 15:16:06
|
| [2014-03-14 15:13:32] |
| Carl71 - Posts: 125 |
|
The demo of rithmic (paper trading servers) uses these servers: Traccia instradamento verso ritpa11120.11.rithmic.com [50.57.39.172] su un massimo di 30 punti di passaggio: 1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1] 2 * * * Richiesta scaduta. 3 6 ms 6 ms 6 ms 151.6.48.6 4 7 ms 6 ms 6 ms 151.6.48.154 5 16 ms 84 ms 10 ms 151.6.6.29 6 13 ms 11 ms 13 ms 151.6.2.34 7 11 ms 12 ms 12 ms 212.73.241.161 8 15 ms 14 ms 14 ms ae-0-11.bar1.Milan1.Level3.net [4.69.142.189] 9 124 ms 124 ms 124 ms ae-8-8.ebr3.Paris1.Level3.net [4.69.142.186] 10 124 ms 125 ms 124 ms ae-73-73.csw2.Paris1.Level3.net [4.69.161.114] 11 123 ms 123 ms 122 ms ae-72-72.ebr2.Paris1.Level3.net [4.69.161.97] 12 122 ms 124 ms 122 ms ae-42-42.ebr2.Washington1.Level3.net [4.69.137.5 4] 13 126 ms 125 ms 125 ms ae-48-48.ebr2.Washington12.Level3.net [4.69.202. 62] 14 122 ms 121 ms 123 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146] 15 123 ms 123 ms 124 ms ae-209-3609.edge1.Chicago2.Level3.net [4.69.158. 225] 16 126 ms 126 ms 126 ms 4.71.248.54 17 138 ms 125 ms 124 ms corea.ord1.rackspace.net [184.106.126.132] 18 126 ms 125 ms 124 ms core1-CoreA.ord1.rackspace.net [184.106.126.125] 19 125 ms 125 ms 125 ms aggr301a-9-core1.ord1.rackspace.net [173.203.0.1 97] 20 139 ms 138 ms 139 ms ritpa11120.11.rithmic.com [50.57.39.172] Traccia completata. Traccia instradamento verso ritpz11202.11.rithmic.com [23.253.217.98] su un massimo di 30 punti di passaggio: 1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1] 2 7 ms * * 151.6.140.72 3 11 ms 7 ms 6 ms 151.6.48.6 4 6 ms 7 ms 6 ms 151.6.48.158 5 14 ms 67 ms 13 ms 151.6.7.45 6 12 ms 12 ms 14 ms 151.6.0.38 7 12 ms 11 ms 12 ms 212.73.241.161 8 60 ms 14 ms 14 ms ae-0-11.bar1.Milan1.Level3.net [4.69.142.189] 9 125 ms 125 ms 125 ms ae-8-8.ebr3.Paris1.Level3.net [4.69.142.186] 10 134 ms 126 ms 125 ms ae-83-83.csw3.Paris1.Level3.net [4.69.161.118] 11 123 ms 123 ms 124 ms ae-82-82.ebr2.Paris1.Level3.net [4.69.161.101] 12 127 ms 127 ms 127 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5 0] 13 128 ms 127 ms 128 ms ae-45-45.ebr2.Washington12.Level3.net [4.69.143. 222] 14 125 ms 125 ms 125 ms ae-6-6.ebr2.Chicago2.Level3.net [4.69.148.146] 15 126 ms 125 ms 126 ms ae-212-3612.edge1.Chicago2.Level3.net [4.69.158. 237] 16 129 ms 128 ms 129 ms 4.71.248.54 17 140 ms 127 ms 127 ms corea.ord1.rackspace.net [184.106.126.132] 18 141 ms 141 ms 141 ms corea-core6.ord1.rackspace.net [50.56.6.133] 19 137 ms 137 ms 137 ms aggr1501a-8-core6.ord1.rackspace.net [162.209.19 .231] 20 126 ms 124 ms 126 ms ritpz11202.11.rithmic.com [23.253.217.98] Traccia completata. Date Time Of Last Edit: 2014-03-14 15:19:22
|
| [2014-03-14 15:24:33] |
| Carl71 - Posts: 125 |
|
Could you please ask Rithmic about this question? Rithmic 01 Europe server path is the same of the others? Based on upon information we could say that there are not differences between Europa and USA servers Thanks Date Time Of Last Edit: 2014-03-14 15:24:56
|
| [2014-03-14 22:30:18] |
| Hendrixon - Posts: 130 |
|
the DTC bridge program that we use with Rithmic could introduce up to something like 100 ms of delay. It was hard to solve this
100ms?? Was this solved? What is the current added latency? |
| [2014-03-14 22:47:48] |
| Hendrixon - Posts: 130 |
|
Carl71, Rithmic's paper trading system is of course located in their Aurora Illinois data center(where also the CME data center resides), so you'll see same latency as the US stream with the live trading account. Also you can't do a ping test and assume that this is the real latency. there are lots of other variables to consider. Basically without comparing millisecond timestamps (which SC decided not to support) coming out of Rithmic's Aurora sub system to the time they arrive locally inside your SC instance, you will never ever know what is your **real life** (pop to screen) latency, and you'll never know if you have other latency problems during your trading hours. |
| [2014-03-15 02:19:49] |
| |
|
100ms?? Was this solved? What is the current added latency? Basically without comparing millisecond timestamps (which SC decided not to support) We know. We did try to work towards this last time it was discussed but just that it was getting involved and we set it aside.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2014-03-15 02:20:22
|
To post a message in this thread, you need to log in with your Sierra Chart account: