holoscan::SerializationDomainSplitPolicy
BetaThis page is for version 5.0 (Latest) (default).
For other versions, use one of these documentation indexes:
- 5.0 (Latest) (default): https://docs.nvidia.com/holoscan/sdk-user-guide/5-0-latest/llms.txt
- ltsb-2.0: https://docs.nvidia.com/holoscan/sdk-user-guide/ltsb-2-0/llms.txt
- 4.6: https://docs.nvidia.com/holoscan/sdk-user-guide/4-6/llms.txt
- 4.5: https://docs.nvidia.com/holoscan/sdk-user-guide/4-5/llms.txt
- 4.4: https://docs.nvidia.com/holoscan/sdk-user-guide/4-4/llms.txt
- 4.3: https://docs.nvidia.com/holoscan/sdk-user-guide/4-3/llms.txt
- Archives: https://docs.nvidia.com/holoscan/sdk-user-guide/archives/llms.txt
Select compile admission when one Operator serialization domain spans several execution partitions of a process.
Operators that share a serialization domain, such as Python Operators sharing the GIL, never run their callbacks concurrently, so partitions that split such a domain add threads that wait on each other. A split can still be intentional, for example when the callbacks release the domain during long native calls or when the partitions need separate thread placement.
Values
