Minecraft: 1.20.1
Forge: 47.4.9
ImmediatelyFast: 1.5.2+1.20.1

On my 1.20.1 world called Cora World: Mine & Slash, I'm experiencing and observing possible framerate loss, that my framerate's not looking too good than the last time I played on this world and 1.20.1 in months... (possibly like four months or so)

I have Spark in my list to see what's causing my client to lag and when toggling the mods tab in the profiler is causing the most lag and I see that ImmediatelyFast is the second most lag causing mod underneath Xaero's Minimap....

These threads:

in the render thread is consuming 13.80% of my frames (client) which is bad actually, these threads needs to be optimized...

Also, apparently this mod has built in shaders????
If it does then I need to turn them off because that's what's possibly causing my client to lag!....
For an example, just like in my 1.12.2 world with The Betweenlands's built-in shaders (which I've turned them off btw) as well as another one of the mods I have in my 1.12.2 mod list (but I don't think that I can turn it's built-in shaders within it off sadly...)

Even though I've provided screenshots but here's the spark profile when I did "/sparkclient profiler start --timeout 60": https://spark.lucko.me/3ZaSs8Wyj2

Please fix this so that my worlds in 1.20.1 and 1.21.1 won't be so laggy with unoptimized (*and unsafe possibly?) threads.....

*(I don't know if these threads are safe or not...)

One more thing, I've already reported to Xaero's Minimap with my findings in hopes to make my 1.20.1 and 1.21.1 worlds a bit more optimized on the client side, since now my focus for optimization is my client, not really the intergraded server.

You are reading the spark results wrong. ImmediatelyFast wraps some Minecraft methods, which causes spark to wrongfully attribute used CPU time to ImmediatelyFast. If you look at the stacktraces, you can see that ImmediatelyFast calls Minecraft code, which then actually uses the CPU time

Huh, Why did spark call a false positive for calling out the mod being the second most laggiest mod in my game?...

In this case, maybe Spark also done a false positive with Xaero's Mimimap's Entity Radar as well?...

Huh, Why did spark call a false positive for calling out the mod being the second most laggiest mod in my game?...

In this case, maybe Spark also done a false positive with Xaero's Mimimap's Entity Radar as well?...

Reading spark results isn't as easy as looking at the overview, which groups by mod. Mods have the ability to replace/wrap Minecraft code, which makes this spark feature misleading. If a mod wraps Minecraft code, spark attributes the CPU time the Minecraft code needs to the mod, even tho the mod replaced that code somewhere else. You should learn how to properly interpret spark profiler results before opening issues

I thought that I knew how to use Spark to fix fps issues but Ig that I don't know how it works or how to use it as a tool to fox fps problems...
Obviously the internet won't really provide me the answer...
Sorry for wasting your time with a false positive as I've wasted my time trying to interpret and understand Spark profiles when I clearly don't understand them...
I do understand crash reports and logs to some degree but a Spark profile? Nope.
Guess I'll stop using Spark when I don't understand how to view them properly....