Be the first to post for 'Performance Profiling 101'!

[sampattuzzi]

If you’re reading this, there probably aren’t very many posts yet. But don’t worry, you can be the first! Either create a new post or just reply to this one to say ‘hi’.

[Robert_Tao_Wu]

My worse max load should be .0001746 Milliseconds

[ben]

Great to have you with me at the forefront of this section, like a wingman :-). @DanM is quiet?

[Gemini]

Cycle Waypoint Index – .000015 ms
ExecuteUbergraph_ChooseNextWayPoint – .000066 ms
GetPatrolPoints – .000012 ms
ReceiveExecuteAI – .000162 ms (Worst Max Load)
Set Next Waypoint – .00003 ms

[Marc_Carlyon]

1. Cycle Way Point Index – 0.001547 ms
2. ChooseNextWayPoint – 0.006154 ms
3. Get Patrol Points - 0.001751 ms
4. RecieveExecuteAI – 0.006698 ms (Highest Max Load)
5. Set Next Waypoint – 0.004335 ms

[Jason_Sharp]

Top Max Load: ReceiveExecuteAI at .000093ms

[CaptainProtonCz]

• My worst load: 0.133 ms * 0,023 = 0,003059 ms
• Also I noticed that my graph is not flattening out, so would that indicate my machine is slow? What does it really tell?

[pdoogs]

My Max Load was 0.0024 ms for Receive Execute AI.

[ZacharyDK]

Worst max load was from receive execute AI. 0.232 * 3.5% = 0.00812 milliseconds. Others are comparable but the average is so low it shouldn’t be a problem.

[GameLover]

My max load is Receive AI with max load of 0,00000135 MS.

[ktonegawa]

not sure if i did this correctly but here it is:

average fps: 1sec / 0.021876 = 45.7fps
heaviest call: ChooseNextWaypoint_C.ReceiveExecuteAI
called every: 45.7fps x 0.005 = 0.2286seconds