Redax uses "one" processing stage where a chunk of data from random digitizers is sent to a random thread for processing and compression. This makes tracking timestamp rollovers potentially more difficult, and also isn't the most effective way of load-balancing the CPU needs of processing and compression.
A better solution would be to split processing and compression into separate stages.
Redax uses "one" processing stage where a chunk of data from random digitizers is sent to a random thread for processing and compression. This makes tracking timestamp rollovers potentially more difficult, and also isn't the most effective way of load-balancing the CPU needs of processing and compression.
A better solution would be to split processing and compression into separate stages.