You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What are the design considerations for QUIC_EXECUTION_PROFILE_TYPE_MAX_THROUGHPUT compared to QUIC_EXECUTION_PROFILE_LOW_LATENCY?
From the code, I observed that in "max throughput" mode, a separate thread is created for each worker, and "soft-affinity" is set to an ideal processor.
Could you clarify under what circumstances the thread owned by the worker is executed? It seems that the CXPLAT_WORKER directly invokes the callbacks of QUIC_WORKER, and the worker thread only wakes up on events such as new connections or operations.
Additionally, how does this approach enhance throughput in "max throughput" mode compared to the "low latency" option?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What are the design considerations for
QUIC_EXECUTION_PROFILE_TYPE_MAX_THROUGHPUT
compared toQUIC_EXECUTION_PROFILE_LOW_LATENCY
?From the code, I observed that in "max throughput" mode, a separate thread is created for each worker, and "soft-affinity" is set to an ideal processor.
Could you clarify under what circumstances the thread owned by the worker is executed? It seems that the
CXPLAT_WORKER
directly invokes the callbacks ofQUIC_WORKER
, and the worker thread only wakes up on events such as new connections or operations.Additionally, how does this approach enhance throughput in "max throughput" mode compared to the "low latency" option?
Beta Was this translation helpful? Give feedback.
All reactions