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

Multiple d3 clients: how many cores per d3/DB?

Sulixes

New Member
Joined
Oct 22, 2012
Messages
83
Reaction score
0
Im currently using YAR with 7 bots and assigning 1 core (via core affiinity) per diablo3/DB instance.

With 7 instances running, im about 25% CPU usage on my i7 overclocked.
it uses up 12 gig total ram out of my 32 available.
GPU load is 12%


however, d3s seem to crash often, and sometime my computer lag-spikes for extended durations.

i've setup each demonbuddy priority to "avove average" and diablo instances to "high"


How do you guys go about setting processes priority and core affinity for multiple bots so that it run flawlessly and doesn't impact my other computer activites?
 
AMD 7850 for some reason has issues with Diablo 3 -- Do some google searches for common issues with the 7850 and Diablo 3. I'm not sure why, but there are some gripes around the community for it.

Couple things:
Are your GPU drivers up-to-date? [[There has been some confliction with current AMD updates to their GPU(s) and Diablo 3, not sure why]]
Are you overclocking your card (I'm assuming yes).
 
is d3 crashing, or db, because there is a difference. lately people have had problems with db crashing
just making sure your specifying the right problem
 

If you've manually overclocked your VC, you might want to re-do it. You might have an unstable OC (every game is different when it comes to GPU OC.) I'm also assuming you've enabled vsync with your video card?

Also, try pushing your graphics drives back 1 update (i.e. if you're on version 10.2, rollback to version 10.1) and see if this resolves the issue.
 
If you've manually overclocked your VC, you might want to re-do it. You might have an unstable OC (every game is different when it comes to GPU OC.) I'm also assuming you've enabled vsync with your video card?

Also, try pushing your graphics drives back 1 update (i.e. if you're on version 10.2, rollback to version 10.1) and see if this resolves the issue.

i did not overclock the GPU, only the CPU.

it worked absoluetly fine when i was using VMs

im pretty sure the issue lies in assigning cores/priority
 
have you tried assign two cores per client?
or not assigning cores at all?
 
i did not overclock the GPU, only the CPU.

it worked absoluetly fine when i was using VMs

im pretty sure the issue lies in assigning cores/priority

I wouldn't set priorities or affinities unless it's absolutely necessary.
 
Would recommend not manually assigning cores or priority... Will always cause the OS to become unstable...

Have never scene a scenario where it worked as expected w/o problems.
 
Would recommend not manually assigning cores or priority... Will always cause the OS to become unstable...

Have never scene a scenario where it worked as expected w/o problems.

I've done it alot (server side). Typically you only set higher priorities to applications that your customer deems as the biggest "money makers"...
 
Well when I made that statement, my train of thought was strictly within the realm of desktops... Server-side applications and hardware are a different story all together...
 
The OS is pretty good at giving threads fair runtime. I've found that I get smoother performance by not trying to dictate where the threads go.
 
Back
Top