Open Hlibix opened 3 months ago
Hello.
Comparing specific test cases, Unio does not have an advantage in execution speed. It was slightly faster, but only by a margin of error. That is not the intended improvement. That's why I didn't put the graph on it.
What the library is intended to do is to improve the load from the GC.Collect phase of the entire application process and the total memory footprint of the entire application process.
This is difficult to measure because it is process-wide. What can be clearly measured is the reduction of GC load.
Reducing GC Alloc in the Unity environment will improve the above issues. This is a general statement. (GC Alloc for byte sequences that are not needed as C# data types is clearly a waste of resources.) There may be some data on reducing the load on JobSystem when using Unity's Temp allocator.
The motivation states that the library has been developed to reduce the performance penalty of the apps. But, only GC alloc results are provided
Can you add the time performance comparison?