hi
@Radek Tomšej! you're correct that there's no multithreading executor, and there's no ECS executor (although there is an
ECS run launcher, which launches an ECS job per-run rather than per-op). Depending on what exactly those I/O bounded operations are, sometimes it can make sense to just group that computation into a single op (within the bounds of an op, you can use whatever multithreading constructs you want). Of course, you lose the observability benefits of separate ops but it also gives you maximal flexibility