Cool, for me it's just 12.9M ticks, the rest is depth amplified by sell and buy side which if you calculate comes to 140M records(12.9*(10+1)), it's not ticks so to speak. From that POV I might have lesser incoming than you.
Hope this helps, you're right, it's about the same. I might not have calculated it properly back then or indexed on things which weren't needed perhaps.
Total rows: 142134767
Size on disk: 780MB
Uncompressed size: 5.13GB
Filesystem Usage: 1.5G …
This is from today, i.e. there are about 2M ticks where the timestamp and ltt is more than 60 s(ideally I guess that should be fine? since it comes to liquidity of instrument etc.) but it shouldn't show up in `ticks` also is what I feel(as a change …
What all things are you storing at your end? Let me re-verify. I do not have the python setup with me anymore. Still fixing up a few things, so I'll get back when I can.
Thank you Nivas, we can close this thread. I didn't look into in depth of how these ticks look like but I can be on the lookout for these and ignore them.
It also happens when kite starts up pre-market hours I guess. Maybe a small section in offici…
To anyone coming from the future, the golang version is much much better. I just got done with an initial implementation porting the logic from Python to Golang and it seems to be going okay.
Will try to update this thread if things work out proper…
Some updates from today, after a bit of modifications and removing bloated validations/logic.
load average: 5.51, 6.01, 5.65
Mem: 3816 1655 112 936 3231 2160
c6i.large
It's doing much better than …
Hi @mrkaran, thank you.
I resized it to c6i.large. The current uptime is 04:43:04 up 1:32, 2 users, load average: 9.43, 9.40, 9.38. I'll read up a bit more on load averages(as I've been doing for last couple of years diligently) to see if this…
It's a huge step forward when prices were reduced from 2000/- to 500/-. Might I suggest to reconsider our earlier discussion https://kite.trade/forum/discussion/comment/47284. If all API endpoints could support this then maybe it allows for a long t…
Thank you for the update @sujith , I was hoping to see support for IPv6 only networks. Is there a possibility/plan to include it in the long run? With a yes/no to this query I guess we're good to close this thread.
Hi Team,
Can we at least get an ack on this? And if possible, some tentative timelines on when we can expect this to be implemented? Have been following it up for quite some time now and there has been very little engagement here.
Hi @sujith,
Any update on this thread if you got a chance to look at it? I can still reproduce this at my end
wss://ws.kite.trade ( Fails with IPv6 )
root@postgresql01:/tmp# ./websocat wss://ws.kite.trade
websocat: WebSocketError: WebSocketError: …
Hi Sujith,
Thank you for taking a look here. If you could see above ws://ws.kite.trade returns Network unreachable on an IPv6 only network while a different server responds back.
I have been able to request CSVs etc. on an IPv6 only network from …
Hi Team,
Could you please let us know if Websockets support IPv6 ?
On an IPv4 network
./websocat.x86_64-unknown-linux-musl ws://ws.kite.trade
websocat: WebSocketError: WebSocketError: Received unexpected status code (400 Bad Request)
On an IPv6 o…
