doesnt need logs, its been a problem across osbot on multi platforms during its lifetime, Dev's dont need much info because its happening to everyone across the board. Educated guess on my part would tell me that its something to do with the mirror process. Though osb2 has always used alot more cpu than its competition anyway. cba to explain myself more as the picture is self explanatory.
1 client = 50%+ thats not commercially viable. I have a computer with very good specifications. For the average user (14-18 years of age) wont have a high spec computer and such will struggle to run 1 mirror client without lag let alone more than 1.