I don’t believe those numbers are accurate. For example, they are reporting String.Split taking 172KB. I don’t think that performing a split operation on a 30 character string requires almost 200k of memory. The similarly, calling type.Name doesn’t require 283K. I doubt it uses 283 bytes. In addition, the assembly sizes are skewed because you are running in the editor.
In general, the profiler serves as a guide for finding problems, but can be wildly inaccurate at times.
In Rain 1.x , when I load BT ( ~ 50 nodes, half of them is custom class in global assembly ) in runtime, it didn’t drop too much frame-rate, but after upgraded to Rain 2.x, it drop significantly, could you have any performance test case for this situation ?