When starting acquisition, the CVB acquisition engine will select a default size for the flow set pool to use (i.e. how many frames can be buffered at once). In many situations, this value is not optimal for the given application and system, and it is beneficial to tweak this to get maximum performance at the lowest memory usage. CVB provides the functionality to do this with little effort by calling CVB::Driver::Stream::RegisterManagedFlowSetPool
with the required number of flow sets.
Note: Error handling has been omitted from the above example.
CVB::Driver::Stream::RegisterManagedFlowSetPool
.CVB::Driver::Stream::RegisterManagedFlowSetPool
multiple times, it is recommended to call CVB::Stream::DeregisterFlowSetPool
between. Internally, CVB will allocate the new Cvb::FlowSetPool
and then delete the old one, which will lead to spikes in the memory usage as both the old and new Cvb::FlowSetPool
s are instantiated for a brief moment, which may lead to issues on memory-limited systems.CVB::Driver::Stream::RegisterManagedFlowSetPool
. New calls to CVB::Driver::Stream::RegisterManagedFlowSetPool
will override previous calls.