What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Cpu usage

pantasd

New Member
Joined
Jan 15, 2010
Messages
14
Reaction score
0
Are they any plans to reduce the CPU usage of DB ?
Or releasing a lite launcher would be great :)

If the DB would take 1/3 less cpu i could run 4 more bots :(
 
read the patch notes to .217

EDIT: its in .215 but also read .217
 
Changelog .215

General


  • Updated for 1.0.4.11327
  • CPU usage should be significantly better


but still it takes alot :(
 
but still it takes alot :(
It does indeed. To be honest, I'm not quite certain what they're basing the claim of reduced CPU load off of. Version 204 was significantly, tremendously less CPU-intensive for me in large combat scenarios than 220 is. Either DemonBuddy or Belphegor absolutely chokes on itself when it has to fight large groups of enemies and do target-selection. It's pretty miserable.

Hopefully they get it all sorted soon. Nesox is probably working hard to resolve all this. Just be patient.
 
it's defenitely true.
db consume high cpu resources than other bots.
 
i used for sometime hellbuddy he uses 200mb ram and 0 cpu for 1 or 20 instances always the same


but DB makes more gph so its ok if they would reduce the cpu usage :)
 
it went down a lot for 217 but went back up for 220 for me
 
My CPU usage with 204 was at 90-100% with 2 bots (Celeron G530). Each demonbuddy instance was between 25 and 30%, and each D3 was 20-25%. With 215 that went down to about 50% overall, DB at about 14% per instance, and D3 at 10-15%. Not sure what happened with D3, but the load definitely went down.

Running 220 now, with the same results: for me, CPU usage was cut in half from 204.
 
My CPU usage with 204 was at 90-100% with 2 bots (Celeron G530). Each demonbuddy instance was between 25 and 30%, and each D3 was 20-25%. With 215 that went down to about 50% overall, DB at about 14% per instance, and D3 at 10-15%. Not sure what happened with D3, but the load definitely went down.

Running 220 now, with the same results: for me, CPU usage was cut in half from 204.

I think i'm experiencing somewhat the same. My diablo takes 5 - 8 % and db 5 - 7% as well : )
 
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.
 
Last edited:
I too am in the same boat, i can run up to 6 clients smoothly on my rig, but with DB, i can run 4 max and thats including some choppiness.

The majority of us know that DB does use a significant amount of processing speed and im sure they are aware of this issue as well and is working on fixing it. Just a waiting game, but i undesrtand your frustation as well.
 
I agree with you guys, DB CPU usage is insane.
I just started today but already thinking about asking a refund.
 
Yes my CPU usage went through the roof with the lastest updates. Right now Im at 60% running 3 d3 clients with DB. Before with 204 i was at 30...
 
bump, this need to be adressed. we need to hear from the devs, every new DB version uses more and more CPU and it's killing my profits.
 
Since swapping routines to Giles' Combat Replacer, the majority of my CPU crunching and lag has gone away. For me, clearly it was Belphegor that was destroying my system.

I recommend everyone give that a try and see if it fixes your problems.
 
Since swapping routines to Giles' Combat Replacer, the majority of my CPU crunching and lag has gone away. For me, clearly it was Belphegor that was destroying my system.

I recommend everyone give that a try and see if it fixes your problems.

I've tried every combat routine/plugin out there, it doesn't help.

I honestly hope this CPU madness doesn't have something to with DB devs cramming their DRM ("nav server"? lol) in Demonbuddy, whether it makes sense or not, just to keep up with the "license" sales model. I have some programming background and the only reasons I can come up with for explaining it are either forced DRM mechanisms or very sloppy, redundant coding. The WHOLE Diablo III client uses significantly less CPU, even in combat with a lot of enemies ingame. And we're talking about a whole game; games usually are very CPU innefficient by their complex, diversified nature. The demonbuddy CPU spikes also seem awfully coordinated with receiving paths from the "nav server"...it's just insane.

I'm still waiting for an explanation of any kind from a dev, they MUST know what is causing this CPU usage, and if they're planning to do something about it. I feel I deserve an explanation before buying any more licenses, as this affects me directly and might make me just go buy another bot. It's cheaper than getting a new CPU.
 
Last edited:
Back
Top