compuforexpamm posted:
   Steve,

If you are interested, I have attached a monitor indicator that I wrote. It basically counts the incoming ticks and then compares the number of counted ticks with the volume of the tick(which is nothing more than the number of ticks sent out by the broker). The indicater converts this to a score out of 100(ie %). Just place the indicator on a 5M chart.

My VPS typically runs at about 95% on average which means that I lose about 5% of my ticks. My home computer runs at closer to 70%

As you indicated, this would be currency specific but used on a busy currency will give you a good idea of the quality of your connection.


Kenny,
That's genius. Thanks for sharing it.
Best regards Steve

   compuforexpamm posted:
   Steve,

If you are interested, I have attached a monitor indicator that I wrote. It basically counts the incoming ticks and then compares the number of counted ticks with the volume of the tick(which is nothing more than the number of ticks sent out by the broker). The indicater converts this to a score out of 100(ie %). Just place the indicator on a 5M chart.

My VPS typically runs at about 95% on average which means that I lose about 5% of my ticks. My home computer runs at closer to 70%

As you indicated, this would be currency specific but used on a busy currency will give you a good idea of the quality of your connection.

Thanks for sharing kenny, appreciate the effort :D.

To add on to Barry's info, you might also want to check your net statistics to confirm that you have the right IP address.

Full instructions written for my mother in mind:
http://raidenworks.com/2012/03/10/latency-to-your-broker/

I was talking to a friend and he mentioned that it could also possibly be that the iVolume picks up all old ticks that the Market Watch queue might dump in favour of a better refresh. e.g. 10 ticks come within a span of 0.1 seconds and the Market Watch chooses the last one to present, while iVolume logs all 10 of them.

   Raiden posted:
   I was talking to a friend and he mentioned that it could also possibly be that the iVolume picks up all old ticks that the Market Watch queue might dump in favour of a better refresh. e.g. 10 ticks come within a span of 0.1 seconds and the Market Watch chooses the last one to present, while iVolume logs all 10 of them.


Hi Raiden,

Sorry for the late reply. I think all the scenarios you mention are entirely possible. I would be lying if I said I understood all the nuances of how the platform connects to a broker.

This is why I am not too stressed about not seeing 100% on my indicator. It typically runs at 90%+ which I would call a benchmark......if I see it drop below that I would start asking questions? It is also useful for highlighting periods where either the VPS or the broker has caused a disconnect.