Question Profiler.FlushMemoryCounters

I see this function taking up about 15% of my frame (in the "Others" category) at 60fps when profiling. It shows up when I uncomment the part where I create about 8000 of my custom sprite particles. (These are not game objects, they're plain C# objects which call DrawMesh to render themselves)

If this Profiler function is soley responsible for the "Others" contribution, I shouldn't worry about it? Does it look like it's the case from this screenshot?

I included 2 screenshots - one before selecting the Profiler.FlushMemoryCounters function in the hierarchy, and one after;



Perhaps it's a situation where I don't want it to track these 8000 objects in this way, though it's hard to know how to track down the problem.

What's wierd is it's just the creation of these custom objects which cause the frame to be consumed by Profiler.FlushMemoryCounters every frame, I've commented out everything else so that these objects are not being updated or rendered. So I guess it's the profiler doing something with them every frame that's causing the performance hit?

 

Thank you, where would I find this Memory Profiler Module to remove it? I think I may have installed something like this for another contract project. But I can't find anything in the Package Manager by that name, and the dropdowns on the Profiler window just toggles the view of the module outputs.

This is my version under About (is there any way to click a button to copy this text without having to manually type out each character?)

 

Does it's cost scale with the number of performance counters in my app? I'm seeing a 2.5ms cost on Quest 2, which is pretty brutal, at that point I'm missing Vsync w/ it on, which makes it a catch-22 situation. If I attach the profiler, which I need to do to get profiling information, then the profiler ends up taking a big chunk of my frames and messing up all the timing info.