-
-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get Announcement with latency #175
Comments
Binance changed it's query parameter caching strategy to serve more requests from cache. They've reduced the parameter space. For example their API used to accept every page size from 1 to 200. But now it's valid values are 1, 2, 5, 10, 15, 20 and 50. It returns 20 articles for any other value. They use AWS CloudFront for caching. CloudFront has cache edge locations and your requests are handled by the closest edge location. Your best bet may be utilizing many edge locations(by placing nodes in different physical locations) and hope some of them misses the cache and hits the origin server. |
Could you send me a PM on twitter? @MilanoCuts |
Could you send me a PM on twitter? @MilanoCuts @shoestar @Jrjy3 |
Did you manage to do it? |
Did you manage to improve it? |
I tested the announcement API for a few weeks and I noticed that the API data is always delayed than the real
releaseDate
of the announcement.So I tried to use proxies to pretend the request from different countries, like the USA, Canada, Singapore, Japan, and I found the latency is different for each country.
The fastest I can reach is about
15s
now, and I don't know how to improve it.And I recently found every notification of announcement is delayed than before, like telegram, binance windows client and etc
So, I guess the binance did something with the API, it was done deliberately by the binance programmers so that a narrow circle of people could react to the news faster than everyone else.
Any idea of this and how to improve it?
The text was updated successfully, but these errors were encountered: