1. Home
  2. Categories
  3. Bugs
  4. Issue with tick data when large number of tokens are subscribed

Issue with tick data when large number of tokens are subscribed

Bugs
Log in to reply
  • N

    @Moderator_1 @Moderator_2 @admin123 Any update on the issue? I am not able to launch my strategy because of this

    0
  • A

    I'm also facing similar issue with feed data, In my case I subscribe to around 200 tokens (Nifty Option Script) and able to get tick data properly.

    But the problem is when I try to create candles out of that data, it dosen't match with angelone candles, There was a slight difference.

    Also there're two timestamps in websocket 2.0. exchange_timestamp & last_traded_timestamp I'm not sure which one to considered while creating candles.

    Though I tried both and none of them was matching with angelone candles

    Note:

    I've already tried Historical API (getCandleData) which is even worse.

    It gives accurate data for older candles Which means if I request for last ten 5 minutes candles the first 9 candles were good but the last candle (latest) was not matching with angelone.

    I absorbed that even angelone takes some time to settle down the candle data.

    F.e
    If the time is 12:00 and you request for 11:55 candle (Nifty Option Script), The received data was inappropriate, But if you request the same at 12:05, 11.55 candle should settled but 12:00 candle will be inappropriate.

    0 A 1 Reply
  • A

    @Moderator_1

    0 A 1 Reply
  • A

    @Ananth said in Issue with tick data when large number of tokens are subscribed:

    @Moderator_1

    @Ananth said in Issue with tick data when large number of tokens are subscribed:

    I'm also facing similar issue with feed data, In my case I subscribe to around 200 tokens (Nifty Option Script) and able to get tick data properly.

    But the problem is when I try to create candles out of that data, it dosen't match with angelone candles, There was a slight difference.

    Also there're two timestamps in websocket 2.0. exchange_timestamp & last_traded_timestamp I'm not sure which one to considered while creating candles.

    Though I tried both and none of them was matching with angelone candles

    Note:

    I've already tried Historical API (getCandleData) which is even worse.

    It gives accurate data for older candles Which means if I request for last ten 5 minutes candles the first 9 candles were good but the last candle (latest) was not matching with angelone.

    I absorbed that even angelone takes some time to settle down the candle data.

    F.e
    If the time is 12:00 and you request for 11:55 candle (Nifty Option Script), The received data was inappropriate, But if you request the same at 12:05, 11.55 candle should settled but 12:00 candle will be inappropriate.

    @admin @admin123 @Moderator_1 @Moderator_2 @Moderator_3

    0
  • M

    Hello @DevPatel

    There is a limit like @chetansuri as mentioned.
    For each client code maximum 3 parallel sessions are allowed and 1000 token as well.

    Regards,
    SamrtAPI Team

    0