The current implementation of rap-worker uses an O(bad) algorithm for scanning
the recordings for processing, where O(Bad) is at least greater than O(n^2) :-)
On servers with large (>1000's) of recordings, the rap-worker will consume
large amounts of CPU.
Original issue reported on code.google.com by ffdixon@gmail.com on 3 Aug 2014 at 9:00
Original issue reported on code.google.com by
ffdixon@gmail.com
on 3 Aug 2014 at 9:00