Hi everyone, i m near the end of the writting of my new performance, but i m deeply fighting performances issues, and every time i m trying to fix it, LLM are pointing to GC and one processor being too much involved.
im hardly running at 17fps. i have 350 layers and a infrustrum condition to manage them. All textures are representing 190 Mo and being in png, in 8 bits with alpha.
i dont see how basically to see where is the bottle-neck in my patch.
is there any way to snif what s going on with garbage collector usage, a kind of monitor ?
And is there any ressources about GCPinner ? I dont see how to use it ?
thank you for your help
I m replying to myself, and finally its Claude IA, who suddendly, entered with the right tools on this simple question i had many time asked about (on forum, on elments, and to claude) : how to evaluate what is in garbage collector, who is blocking killing ressources ect…
Here are the tools to install from command exe and the dot net runtime :
dotnet tool install -g dotnet-counters
dotnet tool install -g dotnet-trace
Dot Net counter will help to see if there are objects GEN 1 stealing ressources, and to estimate more accurently whats going on (with the help of a tchat bot)
Dot net trace enables a recording wich can be analysed by Claude, and readen by Perfview exe ( if you know the data inside and how to read them).
Tracing has today enable me with Claude IA to go from a 16fps bottle neck to a 24 fps (and 35 when not on strong scenes).
The collect of dotnet trace is launched like this :
dotnet-trace collect -n vvvv --profile gc-verbose --duration 00:00:00:10
I still not understand how i passed more than one year having deep pain ass on that framerate, without any suggestion about those dot-net-tools and the help of an LLM to analyse them.
My personal problems where :
forget Try region, isAssigned is your friend
and most lightly SetValue(Channel) vs EnsureValue(Channel)
I hope this will help anybody in my situation ( not deep Sharp coder, artist or low parch coder)
