جميع الكتب

مهني

1 Markets I: The Ecosystem and Exchange-Traded Marketsالأسواق عبر الإنترنت 2 Markets II: Rates, FX and Creditالأسواق عبر الإنترنت 3 Markets III: Commodities, Energy and Cryptoالأسواق عبر الإنترنت 4 Quantitative Methodsالأساليب عبر الإنترنت 5 Derivatives and Volatilityالمشتقات عبر الإنترنت 6 Rates, Credit, XVA and Riskالفائدة والائتمان والمخاطر عبر الإنترنت 7 Research Craft: Predictors, Backtests, Measurement, Portfoliosالبحث عبر الإنترنت 8 Strategies I: Equities and Futuresالاستراتيجيات عبر الإنترنت 9 Strategies II: Volatility, Relative Value, Macro and the Bank Desksالاستراتيجيات عبر الإنترنت 10 Microstructure and Executionالتنفيذ عبر الإنترنت 11 Market Making and High-Frequency Tradingصناعة السوق عبر الإنترنت 12 Machine Learning for Marketsتعلم الآلة عبر الإنترنت 13 Low-Latency Softwareالتكنولوجيا عبر الإنترنت 14 Networks, Hardware and Trading Infrastructureالتكنولوجيا عبر الإنترنت 15 Research, Data and Risk Platformsالتكنولوجيا عبر الإنترنت 16 The Desk and the Firmالشركة عبر الإنترنت 17 The Industry: Firms, Roles and Careersالمسارات المهنية عبر الإنترنت 18 The Interview Bookالمسارات المهنية عبر الإنترنت
التطبيقات حول المدرب تسجيل الدخول ابدأ القراءة

Quantitative Finance · المسرد

ما معنى Event loop, run-to-completion processing؟

يُعرف أيضًا باسم: event loop · run-to-completion processing

Definition 20.1 Low-Latency Software · الفصل 20 — The Strategy Engine

An event loop is a thread that repeatedly takes the next event from its inputs and hands it to the code that handles it. Run-to-completion processing handles each event entirely, including everything it causes, before the next event is taken: no handler is interrupted by another, so a handler never sees a state that another has half changed.

The strategy engine. Every input reaches one thread, which handles each event to completion in an order fixed by rule: the timers due by the event’s time, then the parameters effective by it, then the event. Time is whatever clock the engine was given: a recorded day’s in replay, the machine’s live.
Figure 20.1. The strategy engine. Every input reaches one thread, which handles each event to completion in an order fixed by rule: the timers due by the event’s time, then the parameters effective by it, then the event. Time is whatever clock the engine was given: a recorded day’s in replay, the machine’s live.
اقرأ في الفصل →