Also, not directly related to this PR, but I think there should be a special debug build of MTA, where all this debug stuff is enabled, because in the long run the profiler itself might cause performance issues.

performancebrowser already shows you which functions in a resource use high CPU and what MTA functions (server side only) are using what. I don't understand why anyone would need any more. It would have been time better spent improving performance like the bug that causes GTA SA sounds to use a huge amount of FPS: #1067

Take for example this chunk of code:

setTimer(function()
 for i=1,1000000 do
 end
end,10000,1)

common case when some timer internal logic cause sudden cpu spike,
performance stats even with -d option, doesn't told me that even something is wrong in "xd" resource ( i took a screenshots every time values changed ) :
image

while my approach told me exactly where is the source of cpu spike:
image

That's because there is no function name. I just tested it with a function name via runcode and it gave me:

image

function test()
 for i=1,10000000 do
		
 end
end
setTimer(test,1000,1)

I think that, although a Chromium-based web browser is indeed pretty universal, depending on one to show this profile data is kind of awkward. I think that a browser-agnostic solution would be better, as after all web standards exist so Chrome doesn't become the new Internet Explorer. For example, I use Firefox as my daily web browser, and having to switch to another web browser just for this is, at least, inconvenient.

I suggest generating this profile information in a format that is compatible with profiler.firefox.com, a web application that works on all major web browsers that allows inspecting JSON profile data. I've just uploaded your example profile there, which you can see on this link, and it kinda works, so I'd say the generated profiles are in the right path at least.

Addressing @ArranTuna comments, performancebrowser is more focused on measuring the CPU usage of the Lua VM, memory usage and network usage, while this PR, as I understand it, instruments time-critical regions of MTA: SA source code to generate profile data, like CUnoccupiedVehicleSync::DoPulse. This allows detecting performance problems within MTA itself that are invisible to getPerformanceStats, and may provide insight on what exactly causes some scripting functions to be so slow, for instance.

I've tested this PR and it's, interesting.

CLuaMain::PCall - is this lua scripts executing?

I did this: crun clearPerformanceRecorder() startRecordPerformance() setTimer(function() stopRecordPerformance() setClipboard(getRecordedSamples()) end, 5000, 1)

On play at a spawn:

image

With CIT scripts running in a busy area:

image

Even though I had FPS set to unlimited there are huge gaps in the chart, is this all the stuff that doesn't have a sample added or is it GTA SA code so can't have any sampling on the gaps?

I then did CIT scripts in a quiet area (I had 300 FPS instead of 100):

image

The miliseconds breakdown doesn't seem much different even though FPS was so much different so is that because GTA SA stuff which can't be sampled being what's causing the difference?

Merge conflicts must be resolved.

Also like @Pirulax mentioned performance profiling should be enabled/compiled only for debug builds.

Merge conflicts must be resolved.

Also like @Pirulax mentioned performance profiling should be enabled/compiled only for debug builds.

with current knowlage, rather than enable it in debug mode only we might have a wrappers around some logics that measure performance

public class LuaFunctions : ILuaFunctions
{
 public setElementData(...) { ... }
}
public class LuaFunctionsWithProfiling : ILuaFunctions
{
private ILuaFunctions luaFunctions;
 public LuaFunctionsWithProfiling(ILuaFunctions luaFunctions)
 {
 
 }
 
 public setElementData(...) { 
 begin("function setElementData"));
 luaFunctions->setElementData(...);
 end("function setElementData"));
 }
}
public someLuaDefs{
 public static ILuaFunctions luaFunctions = nullptr;
 public static setElementData(string key, ...)
 {
luaFunctions ->setElementData(key,...)
 }
}
CCore::SetProfilingEnabled()
{
 someLuaDefs::luaFunctions = new LuaFunctionsWithProfiling (new LuaFunctions ())
}