Are you on Windows or Linux?
Windows, using C#
Are you on Windows or Linux?
Windows are known for not being able to handle many socket connections.Windows, using C#
The top 2000 symbols have 99% of the volume so there is effectively no difference in performance between subscribing 2000 or 25000.Yes, I have tried for this solution but every time it's checking our list of 10000 symbols for those symbols which we don't need to handle so it's not solving our issue. I have tried with it. Polygon providing more then 25000 symbols so for 15000 symbols are not in list and loop will work for those also.
Do you get an error 1006 when the websocket closes? If so I am getting the same error.I use Polygon.io, but for realtime quotes, not historical data. During my development I noticed that after about 1000 symbols were being monitored, the websocket would close. So I switched to the NATS interface instead of websocket, and all socket problems disappeared. I do not know if there is a NATS interface for historical data.
Are you on Windows or Linux?
Windows are known for not being able to handle many socket connections.I am on windows and using C# for development.
Do you get an error 1006 when the websocket closes? If so I am getting the same error.