{"id":2197,"date":"2020-03-18T13:13:12","date_gmt":"2020-03-18T05:13:12","guid":{"rendered":"https:\/\/www.clonefactor.com\/wordpress\/?p=2197"},"modified":"2020-03-18T13:13:13","modified_gmt":"2020-03-18T05:13:13","slug":"for-loop-vs-foreach-in-unity","status":"publish","type":"post","link":"https:\/\/www.clonefactor.com\/wordpress\/program\/unity3d\/2197\/","title":{"rendered":"For..loop vs Foreach in Unity"},"content":{"rendered":"\n

Since Unity5.5 have 40kb GC issue.
I’m trying to avoid using Foreach when possible, 

Until Unity3D Team claim they fixed the extra GC issue.
The problem was the “Foreach + List” combination will generator 40kb extra garbage during process.
and this issue should be fixed after 5.5.<\/p>\n\n\n\n

foreach loops<\/strong>
In versions of Unity prior to 5.5, a foreach<\/em> loop iterating over anything other than an array generates garbage each time the loop terminates. This is due to boxing that happens behind the scenes. A System.Object is allocated on the heap when the loop begins and disposed of when the loop terminates. This problem was fixed in Unity 5.5. <\/p> Ref: fixing-performance-problems<\/a> <\/cite><\/blockquote>\n\n\n\n

I don’t believe that, since Foreach are requesting the List<T> to use IEnumerable interface to gain access the data, that should be Unity’s system implementation level bug.
so today I’m trying to run some test on it to find out what actually happen.<\/p>\n

and here is the source code that I used for test cases :
for testing we generate a List<int>, List<object> and Hashset<object> to compare.<\/p>\n

after run an 90000000 (Ninety million)<\/p>\n\n\n\n