I registered on the forums just to post this. PLEASE do something about this, DB team.
CPU usage is a goddamn joke. how is it even possible that Demonbuddy uses significantly more CPU than any Diablo III client? I wish I was joking, but using a simple A-to-B profile with the included Belphegor routine and no plugins consumes way more CPU than a full-blown enemy-plagued D3 client. not only that, but Demonbuddy also "hangs" D3 for a few seconds every time it has a CPU spike (which is very, very often, almost always in combat but also while pathing). I can manually run AND play up to 6 D3 clients in isboxer with no lags at all, smooth as silk, but that is reduced to a maximum of 2 D3 clients if I want to use Demonbuddy. It tops out there too, and the horrendous CPU spikes make the computer unusable.
This should be an absolute priority, I find it a joke that two D3 clients, playing, killing enemies only use a combined 30-40% of CPU and two Demonbuddy clients take up an average of 50-55% BY THEMSELVES, with horrendous CPU usage spikes that hang D3 for a few seconds. It's honestly the main thing that is making me not buy any more licenses, my computer can handle more D3 clients but not any more DB, the CPU spikes just make the characters die because they sit there doing nothing while DB hangs the game for some seconds. And my computer is not a shitty computer either, I use an E6600 @ 3.2Ghz, never had any CPU problems or shortages with any modern games or applications until I used DB.
And don't even get me started on the crashes! When it's not DB crashing itself, it's DB doing something that crashes Diablo III. I've manually leveled 3 characters 1-60, had about 2 crashes while doing it, no more than 3 for sure in many many hours of intensive gameplay. DB makes D3 crash like once every 2 or 3 hours, per client.
I don't wanna be an asshole, but I don't know what else to say besides that you're losing good business by not fixing this.