The query-ing, but also the sorting of the LB stats is done on simple 'list'-based queries in code.
On larger 'lists' oscams process gets very busy, and CPU does rise. Clearing the stats (from RAM) drops the list, and cpu drops immediatly.
This behaviour was already known (to me at least), and only occurs on heavy loaded oscams. (the ones with many request/second).
What is new, to this example, is that aside CPU, the actual ECM times start to rise too. I never seen that before.