PlayerManager uses a single analysis queue/scheduler for regular, preview, and sampler decks. This might be split into separate queues/schedulers that are suspended and resumed internally according to some prioritization strategy.
Currently (as of https://github.com/mixxxdj/mixxx/pull/1624) only the batch analysis is suspended while any ad-hoc analysis in PlayerManager is running. The ad-hoc analysis utilizes half of the CPU cores used by batch analysis to avoid hiccups while performing live. Batch analysis is supposed to be executed during preparation and therefore is allowed to use more cores for maximum performance.
PlayerManager uses a single analysis queue/scheduler for regular, preview, and sampler decks. This might be split into separate queues/schedulers that are suspended and resumed internally according to some prioritization strategy.
Currently (as of https:/ /github. com/mixxxdj/ mixxx/pull/ 1624) only the batch analysis is suspended while any ad-hoc analysis in PlayerManager is running. The ad-hoc analysis utilizes half of the CPU cores used by batch analysis to avoid hiccups while performing live. Batch analysis is supposed to be executed during preparation and therefore is allowed to use more cores for maximum performance.