3 ms·
Yes. Just think of how annoying it is when you have to wait 5 seconds instead of 0.5s for a 2FA message, then multiply that by everything that you ever do with
by analyte123 3y ago
Yes. Just think of how annoying it is when you have to wait 5 seconds instead of 0.5s for a 2FA message, then multiply that by everything that you ever do with your workflow engine. That's not even to speak of cases where running the workflow (e.g. acquiring data) faster is a competitive advantage, although this thing is still probably too slow for truly HFT-level tasks.
- rubenfiszel 3y agoYes it's too slow for HFT, but anything would be too slow for HFT unless it's custom built. You likely want a streaming engine or even hand-optimize all your event handlers to shave-off any nanoseconds.
- samsquire 3y agoJust because I'm interested in this topic. I've been trying to shave nanoseconds on ringbuffers and barriers in C. LMAX Disruptor can send a message between threads in 53 nanoseconds on average. So you can essentially fork control flow in 53 nanoseconds and do 2 things in parallel. Eyeballing my barrier I can synchronize in 42 nanoseconds and up.
- stingraycharles 3y agoAs someone who works with HFT firms, they typically do everything in ASICs or FPGAs anyway, so it’s not a good example.