Optimizing my terrain

[scarlet jacinth]

my marching cubes terrain generator is running terrible and i dont really know how to fix it. heres my code: https://paste.ofcode.org/377XKzxMAnwRpDsLU7rnqgR#

[foggy saddle]

This code has zero optimization

[scarlet jacinth]

thats the problem

[foggy saddle]

Allocations, running the code too often, synchronous on the main thread, not parallelized

[scarlet jacinth]

yeah i know but i have never worked with something this complicated before and have no idea how to fix it

[foggy saddle]

You probably need to profile the code and research improvements step by step

[scarlet jacinth]

thats the profiler

[foggy saddle]

You need to look at the other view and use deep profiling

[scarlet jacinth]

deep profiling froze my unity for 20minutes and pulled all of my ram at once

[foggy saddle]

It tells you exactly how long each method call takes relative to others (mind the profiling overhead that makes everything 10x slower)

[foggy saddle]

Then you have a major error in your code

[scarlet jacinth]

i think ill go to sleep now and look into it again tomorrow

im really tired

[split locust]

You can use profiler markers in specific parts of your code to profile them. This would be lighter than deep profiling.