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

[Trinity][Performance] Execution + lag

R

ryan1cf

New Member
Joined
Sep 1, 2014
Messages
49
Reaction score
1
I'm making a new thread, even though I've seen a bunch of threads from people with this same issue, the constant "[Trinity][Performance] Execution..." issue. I'm not certain this is Trinity or DB because I've tried a mix of different version of DB and different versions of Trinity to no avail.

DB and Trinity worked completely fine for me pre 2.1, since 2.1 it's not working as it used to.

Here's my setup:
Windows 8.1 Pro x64
SSD hdd, Diablo installed on SSD
NVIDIA GeForce GTX 660 wiht 2GB RAM
16 GB RAM
All non essential services stopped in Windows
Diablo 3 screen windowed with all GFX low and low fx enabled.
DemonBuddy v. 1.1.2019.369 - fresh install
Trinity v 2.0.1 - reset
Profile = Adventure Mode Bounties, Community Edition, v 1.03, act 4 non zerg.

What I see is anytime my Demon Hunter encounters any monsters these errors start occuring and occur all the time:

[Trinity][Performance] Execution of CacheManagement.RefreshCacheMainLoop took 1179.52ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache.UpdateBlock took 1182.12ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache took 1183.13ms.
[Trinity][Performance] Execution of HandleTarget.CheckForNewTarget took 1183.38ms.
[Trinity][Performance] Execution of HandleTarget took 1189.03ms.
[Trinity][Performance] Execution of CacheManagement.RefreshCacheMainLoop took 1222.31ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache.UpdateBlock took 1224.44ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache took 1225.35ms.
[Trinity][Performance] Execution of HandleTarget.CheckForNewTarget took 1225.61ms.
[Trinity][Performance] Execution of HandleTarget took 1231.69ms.

I've tried fresh installs of DB and alternate Trinity v. 1.9.8 and so far no go.


Logs attached.
 

Attachments

ryan1cf said:
I'm making a new thread, even though I've seen a bunch of threads from people with this same issue, the constant "[Trinity][Performance] Execution..." issue. I'm not certain this is Trinity or DB because I've tried a mix of different version of DB and different versions of Trinity to no avail.

DB and Trinity worked completely fine for me pre 2.1, since 2.1 it's not working as it used to.

Here's my setup:
Windows 8.1 Pro x64
SSD hdd, Diablo installed on SSD
NVIDIA GeForce GTX 660 wiht 2GB RAM
16 GB RAM
All non essential services stopped in Windows
Diablo 3 screen windowed with all GFX low and low fx enabled.
DemonBuddy v. 1.1.2019.369 - fresh install
Trinity v 2.0.1 - reset
Profile = Adventure Mode Bounties, Community Edition, v 1.03, act 4 non zerg.

What I see is anytime my Demon Hunter encounters any monsters these errors start occuring and occur all the time:

[Trinity][Performance] Execution of CacheManagement.RefreshCacheMainLoop took 1179.52ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache.UpdateBlock took 1182.12ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache took 1183.13ms.
[Trinity][Performance] Execution of HandleTarget.CheckForNewTarget took 1183.38ms.
[Trinity][Performance] Execution of HandleTarget took 1189.03ms.
[Trinity][Performance] Execution of CacheManagement.RefreshCacheMainLoop took 1222.31ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache.UpdateBlock took 1224.44ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache took 1225.35ms.
[Trinity][Performance] Execution of HandleTarget.CheckForNewTarget took 1225.61ms.
[Trinity][Performance] Execution of HandleTarget took 1231.69ms.

I've tried fresh installs of DB and alternate Trinity v. 1.9.8 and so far no go.


Logs attached.
Click to expand...
I'm having the same issues on Win 7 x64, SSD install, but Act 1 rather than Act 4 and a better overall GPU/etc.

Worked fine pre 2.1.
 
In your Trinity Advanced settings, make sure Lazy Raider is unchecked(its a fps hog and will drastically lower your TPS) If you have a perfect profile you can Disable Trinity unstucker that helps me with bumps in 1500+ms spikes (you might get stuck somewhere if its disabled)
 
Thanks PrimeAgent,

Lazy Raider wasn't selected.
Deselected unstucker, issue persists, and actually is much worse today.
New logs attached.

These 9 second ones were the worst:
11:49:14.766 ERROR PerformanceLogger [Trinity][Performance] Execution of CacheManagement.RefreshCacheMainLoop took 9572.27ms.
11:49:14.767 ERROR PerformanceLogger [Trinity][Performance] Execution of RefreshDiaObjectCache.UpdateBlock took 9574.14ms.
11:49:14.767 ERROR PerformanceLogger [Trinity][Performance] Execution of RefreshDiaObjectCache took 9574.88ms.
11:49:14.767 ERROR PerformanceLogger [Trinity][Performance] Execution of TargetCheck.RefreshCache took 9575.09ms.
11:49:14.768 ERROR PerformanceLogger [Trinity][Performance] Execution of TargetCheck took 9575.28ms.
 

Attachments

Tested with Trinity v2.1.3

I still get the 1000-2000 ms performance errors, new logs attached with full debug turned on; the performance errors/lag aren't as bad though.

New issue, during testing a dropped legendary wasn't picked up, that csv attached too; attachment adder wouldn't let me add the .csv or .xls or .xlsx so I zipped up the original itemsdropped.csv. It was a legendary quiver
 

Attachments

Guys.. I just figured mine out..
I couldnt think of anything else so i completely shut down zone alarm and now it works perfectly..
 
I don't have firewall....

Will test new trinity !
 
Still have freeze with Trinity 2.1.3....

[Trinity][Performance] Execution of RefreshDiaObject.MainObjectType took 3539.47ms.
[Trinity][Performance] Execution of CacheManagement.RefreshCacheMainLoop took 3544.96ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache.UpdateBlock took 3546.97ms.
[Trinity][Performance] Execution of RefreshDiaObjectCache took 3560.31ms.
[Trinity][Performance] Execution of TargetCheck.RefreshCache took 3560.58ms.
[Trinity][Performance] Execution of TargetCheck took 3560.95ms.
Click to expand...
 
Thanks FragileAssassin,

I just tried the same thing, I use ESET Smart Security 7, disabled AV and Firewall, didn't make a difference though.

Next thing I think I'm going to try is creating a VM and see about running Diablo in a VM without anything else installed on it.
 
So I couldn't get Diablo 3 to play in a HyperV VM so I decided to uninstall ESET and see what would happen, well DemonBuddy and Trinity work! OMG! So... no AV/Firewall when botting.

So, the "[Trinity][Performance] Execution of" for me had to do with ESET Smart Security 7, even with AV and Firewall protection disabled I still got the errors, only until after I uninstalled ESET, restarted PC then re-attempted does it now work!
 
ESET reinstalled, issued re-appeared.
So, I disabled a bunch of ESET extra's like:
Enable detection of potentially unwanted applications, potentially unsafe applications and suspicious applications.
Also disabled HIPS
Trinity errors gone.

I'm eventually going to narrow this down to which ESET feature is actually causing the issues and I'll report back.
 
I have uninstalled ESET NOD32 and freezes are gone !!!!

We have to wait they fix the conflict, work well before !
 
MaxDps, this is likely an issue with ESET, not Trinity, ESET gets updates too so it may now be interfering with Trinity. I think it's the HIPS in ESET that's causing the issue but I still haven't fully tested it.

Also, I highly recommend using Trinity 2.1.4, because 2.1.3 doesn't pickup Legendary items! It does pickup recipes though.

MaxDps said:
I have uninstalled ESET NOD32 and freezes are gone !!!!

We have to wait they fix the conflict, work well before !
Click to expand...
 
ryan1cf said:
MaxDps, this is likely an issue with ESET, not Trinity, ESET gets updates too so it may now be interfering with Trinity. I think it's the HIPS in ESET that's causing the issue but I still haven't fully tested it.

Also, I highly recommend using Trinity 2.1.4, because 2.1.3 doesn't pickup Legendary items! It does pickup recipes though.
Click to expand...

I haven't update my ESET since months !

Will try the new trinity, but 2.1.3 pick up legendary well here ;)
 
i had only windows firewall on and still got the same issue, even windows defender was off... i dont think this is entirely related to HIPS.
 
SHJordan said:
i had only windows firewall on and still got the same issue, even windows defender was off... i dont think this is entirely related to HIPS.
Click to expand...
Yes ! We are 4 members know with 4 antivirus / firewall different who have the freezes !

And as said before, I haven't updated my AV since months....
 
You must log in or register to reply here.
Back
Top