Realtick problems

[Bsulli]

Quote from Josh Moses:



I think you're mixing up class and attribute. The $LEVEL2$ class didn't exist until about a month ago. The issue is this: servers in the $QUOTES$ class were the primary repositories for &LEVEL2& and &QUOTES& attributes-- ie, Level 2 and Level 1 data. With the vastly increased message rates of the past few months, we found that the servers were *not* able to keep up from a technical standpoint. Thus, we created two new classes, $LEVEL2$ and $LEVEL2NI$, which should keep all internal book data and not lag. RealTick is told that MarketMakers-- your level 2 windows-- should by default look for the &Level2& attribute to which to connect. We have been removing this attribute from $QUOTES$. Thus if your MMakers had never been touched, they would automatically have pointed themselves to the new server class. If, however, you modified your settings and pointed the level 2 portion of your MMakers to $QUOTES$, you would have continued to receive data in your Level 2 because these still contained Level 2 data. However it is no longer your best source. Your best bet is to point the Level 2 portions of anything-- MMakers and 3rd party apps-- to &Level2&. This should have the result of automatically picking the correct class. As to why somebody told you to point your MMaker to quotes a few months ago, I have no idea. The result should have been nothing back then, and detrimental now.

Thanks,
Josh Moses
Townsend Analytics

The only thing I could find any where was class and not attribute. as far as being confused about the two it's beyond me that a charting company would expect an end user to know or even care that these exist, but that's for another discussion and another day.

So moving on If I'm understanding you correctly then in the MMaker window Level 1 price server should point to the "quotes" server and Level2 price server to should point to the "Level2" server. Is my understanding correct then? I couldn't find any listing of "LEVEL2NI" should that appear?

Thanks in advance.

Bsulli

 

[AAAintheBeltway]

Quote from Josh Moses:



If you're getting "bounced off" it means you're having connectivity problems. You ought to try running a constant ping in the morning by going to start | run and typing command or cmd. Hit enter. Type "ping -t beacon.taltrade.com" without the quotes. This will run until you tell it to stop. You'll get a good idea of how long it's taking your ISP to get you to us and how often you're timing out. Again, you may want to give us a call when you're having problems.

Thanks,
Josh Moses
Townsend Analytics

I really doubt that it is a connection issue. It happens too fast, boom I'm disconnected. When I have a bad connection I get a message that it is queing data. Plus it only happens right after the open. I'm alwyas able to reconnect immediately but it is disconcerting. It is not everyday and lately seems to have improved but it will happen every few days. I don't know what your people could tell me if I called, since it is a transient problem.

 

[Josh Moses]

Quote from AAAintheBeltway:



I really doubt that it is a connection issue. It happens too fast, boom I'm disconnected. When I have a bad connection I get a message that it is queing data. Plus it only happens right after the open. I'm alwyas able to reconnect immediately but it is disconcerting. It is not everyday and lately seems to have improved but it will happen every few days. I don't know what your people could tell me if I called, since it is a transient problem.

If you're queuing data, it means that data is not getting through to you from the server. It may mean that you have a connectivity issue, but more likely you are requesting more data than is able to fit through the line or than your computer is able to process. Intermittant connectivity problems will by symptomatic exactly as you describe. My suspicion is that the huge amounts of data flying around your ISP around the open are causing their routers to slow down in passing on information.

Josh Moses
Townsend Analytics

 

[Hambone]

Quote from Josh Moses:



I think you're mixing up class and attribute. The $LEVEL2$ class didn't exist until about a month ago. The issue is this: servers in the $QUOTES$ class were the primary repositories for &LEVEL2& and &QUOTES& attributes-- ie, Level 2 and Level 1 data. With the vastly increased message rates of the past few months, we found that the servers were *not* able to keep up from a technical standpoint. Thus, we created two new classes, $LEVEL2$ and $LEVEL2NI$, which should keep all internal book data and not lag. RealTick is told that MarketMakers-- your level 2 windows-- should by default look for the &Level2& attribute to which to connect. We have been removing this attribute from $QUOTES$. Thus if your MMakers had never been touched, they would automatically have pointed themselves to the new server class. If, however, you modified your settings and pointed the level 2 portion of your MMakers to $QUOTES$, you would have continued to receive data in your Level 2 because these still contained Level 2 data. However it is no longer your best source. Your best bet is to point the Level 2 portions of anything-- MMakers and 3rd party apps-- to &Level2&. This should have the result of automatically picking the correct class. As to why somebody told you to point your MMaker to quotes a few months ago, I have no idea. The result should have been nothing back then, and detrimental now.

Thanks,
Josh Moses
Townsend Analytics

Should We have $LEVEL2$ selected for both Level1 and Level2 price severs to be safe, or leave Level1 server pointed at &QUOTES&, (or $QUOTES$ or "default $QUOTES$")?

rah

 

[Josh Moses]

Quote from RAH2153:



Should We have $LEVEL2$ selected for both Level1 and Level2 price severs to be safe, or leave Level1 server pointed at &QUOTES&, (or $QUOTES$ or "default $QUOTES$")?

rah

Just leave the level 1 portion alone. It should be pointed to the default class, which should be $QUOTES$. Assuming you do nothing to the level 2 portion, it will automatically point itself to $LEVEL2$.

Josh Moses
Townsend Analytics