High spikes: Vector3.op_Inequality

[kfboelter]

Hello.

I am now profiling my project, prior to release.... I am having some complications with Vector3.op_Inequality(). It is generating quite high processing spikes on the profiler. As oyu can see on the attached image, it alone is taking 20ms to process.

Anyone has a clue of how to reduce that? Do you need more info to deal with it?

Regards

[ArenMook]

You're doing a deep profile. The result is highly inaccurate. That 20 ms at deep profile is not even going to be noticeable on a regular profile. Think of it like this. You have an operation that takes 0.0001 ms, but it happens 1000 times. End result -- 0.1 ms taken by the operations. Now you are enabling a deep profile that adds 0.1 ms to each call. Sudddenly your 0.0001 ms operation becoems 0.1001 ms. Do it 1000 times and now your function execution suddenly takes over 100 ms. You're starting to see a problem where there isn't one.

[kfboelter]

ok, I will leave that aside