CPU usage is high while using FyersDataSocket with V3. Event after market hours when no data is flowing, CPU usage is around 15%. I’m using python on windows. Anyone observing the same issue ?
I didn’t observe any such issue.
BTW, I have a question,
When I run the fyers web socket to get the data of bank nifty options (ABC strike price) and put the bank nifty chart of the same abc strike price side by side then I clearly see that the chart shows the data before the web socket data. Also I noticed that the web socket misses some data which I can see in the chart movement.
Is this normal?
Hi @nachi.ckjcr0lp ,
We checked this for you. We are not getting such type of issue. May be your other programs are running that’s why you are getting this High CPU usage.
Kindly check task manager and close the unnecessary program then try again.
Hope it will help.
Thank you
Kindly confirm me which api version you are using.
If v2 then please upgrade to our latest v3
Hope it will help
Please let us know if you are still facing the same issue. We will help you in that.
Hi Sir,
Is the api v3 ready to use. The documentation has so many mistakes as I read in some of the community posts
Please let me know
Yes API v3 is ready for use. We have fixed these mistakes in documentation.
You can use it. If you find any difficulty please let us know.
Thank you
Hello @amitkumar.ppt208-w3m
I am also facing the same issue.
With V2 data update and other things but when upgraded with V3 the gui became very laggy.
If the web socket is not used then everything is smooth.
Hi Pankaj,
For Orders and Positions API endpoints, can you make table to compare V2 and V3 fields. Looks like there are big changes. i know we can use V2.1 in header for V3 but a comparison of pure V3 and V2 fields is required. Thanks.
Last i checked in Docs, V3 response structure is still V2.1 with the header specified as V2.1
Hi @chaitanyakalyani.demat-vbz @amitkumar.ppt208-w3m ,
We’ve improved our WebSocket and updated the order API. Could you please update the SDK and confirm if you’re still experiencing any issues?
There some open while loops in the fyers v3 websocket code. You fix it or just add a sleep of 0.01 secs, the CPU issue will be resolved