Bot working - but lagging on more than capable machine

[ipb]

Hi,

i got my bot working and working well.

some notes:
Questtools 2.1.32
trinity 2.1.12

rrix i think he is, using his rift profile.

dual 8core xeon 2600v2
16gb
geforce gtx680/ tested also with gtx590SLI
dual SSD disks
4GB ramdisk for temp folders etc.
max graphics settings

CPU runs at less than 5% always. however, when running the bot, it will reach a point of sticking every 1 second to 2 seconds and dropping frame rate to 3 to 5 to 10 ... pausing the bot immediately back to 60fps with vsync enabled.

anyone got any ideas?
thx in advance.

 

[HB9290G48]

I'd like to piggy back on this matter. My machine is capable for D3. However, my tick's drop to 5-8 and lags significantly during combat. When not in combat, its smooth. I'm not sure what's going on.

When I play myself, game play is smooth with zero issues. Its only been with the recent Questtools/Trinity update. I even did a fresh install and the matter still persist.
Any help on this will be appreciated.

 

[Dekedynasty]

This occasionally happens with the bot, so expect some minor lag when running.

 

[ipb]

Dekedynasty,

its not occasionally. its all the time and consistent. its losing about 20% of its efficiency with the spikes.

i tried affinity and a few other things. its not a HUGE THING ... but would be nice to get resolved.

 

[Tony]

How To: Attach your HB-DB log file [with pictures]

 

[ipb]

log file attachedView attachment 7472 2014-09-23 08.09.txt

(i hope)

 

[Tony]

whats your back and foreground values?

 

[ipb]

changed from 100 for both to unchecking the boxes. to having different values for both.

have the window on focus and off focus (if thats what its called)

 

[ipb]

check this out:

[Trinity][Performance] Execution of MainFindSafeZoneLoop took 1294.55ms.
[Trinity][Performance] Execution of AbilitySelector.ClassAbility took 1301.57ms.
[Trinity][Performance] Execution of AbilitySelector took 1302.37ms.
[Trinity][Performance] Execution of HandleTarget.AssignMonsterTargetPower took 1302.95ms.
[Trinity][Performance] Execution of HandleTarget took 1958.10ms.

 

[Tony]

set them to 150+ both and also change the D3 process priority above normal