You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Probably the coolest thing about coding a matching engine is the fact that it's a process that runs fully in memory and has to stay up forever.
Can't afford memory leaks, CPU exhaustion, ...
Has to be as perfect as possible.
Current @bitfinex matching engine uptime is 300 days.
We're stabilizing a new version that improves latency by (reduction of ~85%), while guaranteeing much higher execution throughput (up to 10x) during peak times.
But given the current volatility of #crypto markets not sure when we'll decide to release it.pic.twitter.com/zxlPF1uYTo
always innovating paolo papa bless
This is very interesting. Do you backtest the new engine with real logs from the current engine? Have you considered doing a real-time shadow test where all requests are sent in parallel to production and the shadow version?
We have an internal stream replica that is used to feed logs from prod to the new version of the engine. Also we have built more than automated 1000 tests including some hammer scripts that simulate 10k users trading among themselves (with sudo deterministic expectations).
You should write a blog post series similar to what bitmex did in 2018. I would love to read it! I think others could learn a lot too.https://blog.bitmex.com/bitmex-technology-scaling-part-1/ …
ah this is the one actually about the matching enginehttps://blog.bitmex.com/bitmex-technology-scaling-part-2-the-road-to-100x/ …
…………
Are you hiring software engineers?
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
