-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Internal Code
-
Server Programmability
-
Service Arch 2024-03-04, Service Arch 2024-03-18, Service Arch 2024-04-01
SessionWorkflow runs each iteration as an individual task on a service executor. This, however, is not necessary for non-privileged connections that use a synchronous executor, where the connection essentially owns the thread assigned to it by SessionManager. This ticket aims to optimize this code path for the common case by allowing SessionWorkflow to keep running without calling into the executor.