my d3 client is lag spiking on the 5th client? GPU is under 50% load , 7gb of ram spare and cpu hits 40% at the very most.
whats causing this?
i can remember seeing someone having same problem on VS but its down atm :S
all help greatly appreciated.
my d3 client is lag spiking on the 5th client? GPU is under 50% load , 7gb of ram spare and cpu hits 40% at the very most.
whats causing this?
i can remember seeing someone having same problem on VS but its down atm :S
all help greatly appreciated.
make sure u set all video performace on lowest, other than that, it could be some connection problem. Torrents ?
nope because its only the 5th client spiking.
Is it a virtual? Check your disk IO but I doubt it's that as you said it's only the fifth one.
You might want to delete the cache for your 5th client?
its not a virtual , wheres cache in d3 client?
Perhaps that 40% CPU is a bit lying? I don't know, but I cannot see how in multiprocessor environments it should be able to give a combined value of the different processors. Perhaps it can, but parallelisation is a bitch within computing, so perhaps that why? 5 resource hogging programs not distributed properly over the CPUs?
My guess, but I don't know, haven't tried running multiple D3s.
d3 uses hardly any cpu power . it bounces from 20%-35% cpu , graphics is using 30-40% and ram is at 40-45%.
its sharing the clients over all cores.
maybe its you AV or firewall, make sure your disc drives arent connected to...
I have this problem with some of the scripts i run. It only affects D3, I run other games over D3 with no problem. I hardly notice however since the only account I actualy play is my main and I never use anything extra on my main. Honestly I still have no idea why it does this. Usualy with NoAreas or Buddy. Also it doesn't ALWAYS happen. Some apps will lag while others are doing perfect.
Which CPU? If it was say an i7...40% of 8 cores is only half, but with 4 actual core that's nearly 100% - it could be choking up. Have you tried limiting the FPS in the other instances? Check disk IO as mentioned and if possible clone/re-create the VM.