GetTicker: 429: {"msg":"Requests too frequent.","code":"50011"}

Author: Godless, Created: 2022-10-31 20:30:38, Updated:

GetTicker: 429: {msg:Requests too frequent.,code:50011} How do you deal with this error in general?


More

The Little DreamCalling the exchange interface is too frequent, exceeding the exchange limit.

Godless/upload/asset/195913fa877847cbce6a6.jpg This is exactly where the question of where to draw the wind comes from, with sleep or newspaper added everywhere.

GodlessThis is a bug, the code changed the whole policy and got ticker in one place. Or report this error. Silent, also before this error.

The Little DreamExchanges are too frequent to access the interface, check policy.

The Sheep FlyI have a problem with both of them. One hard drive, neither printed.

The Little DreamFor now, there is no support for writing strategies in both languages, but support may be added later.

GodlessDo you have any plans to support Rust and Typescirpt?

The Little DreamThe server can be set up with the minimum configuration and several more servers can be run.

GodlessIt's a good idea to reduce a physical disk, its limited IP seems to be silent, blindly buying such an expensive server.

The Little DreamIf the frequency limit of the exchange interface is not taken into account, the minimum configuration of a server running 5-6 disks is also not a problem. Given the frequency limit, the frequency of access should be considered in conjunction with the specific frequency of your strategy. If your policy is to have a disk that accesses the interface 5 times per second, then a disk will generally not exceed the limit. An increase to 2 disks may exceed the limit. At this point you can only reduce the number of times a disk is accessed. For example, allow a disk to access 5 interfaces in 10 seconds.

GodlessThank you! Generally. Is it better to have a server running several robots and a hard drive? Is there a difference between a single robot + multiple disks and a robot + one hard drive?

The Little DreamGetTicker accesses the market interface, the deep interface. The host should not run as many disks, it is easy to over-frequency. Now if you call 429, stop for 2 hours, then run again should not be reported. It is possible to control the frequency of policy access to the interface.

GodlessThe exchange is sick, for a while it's normal, for a while it's like this, the customer wants to know which interface to give me.

The Little DreamThe principle is simple: if you start with only one physical disk, this access frequency is normal. Then add three physical disks or on this host, the frequency increases threefold. It is easy to exceed the limit of the exchange. In addition, the frequency is too high, you have to stop, at this point no matter how you change it, you will not be able to access it, and the skills will cool down.