Chrome: Performance after latest update?

Check this out, breaks it down right here.
Why are earth are these three lines of code taking so long to execute?Screenshot%20from%202018-08-03%2014-10-12

In the above picture, this.array is has a length of 468000, a.length is 156000

Each vertices has the following { x: # , y:#, z:# , ID: # }

Spending hours pouring over the web for some explanation of the performance issues I’m experiencing I’ve come across a possible culprit. If I had to take a guess as to what is causing the issue it is Chromes method of Garbage Collection. Seems there are a lot of cases where webgl developers notice performance drops with regular updates. More specifically, it seems Chrome handles garbage collection differently for type Arrays, thus Float32Arrays have been the source of a lot of headache for people in the past.

I’m going to convert all my code for moving people over to BufferGeometry and I’ll report back with the results. I’m crossing my fingers here.

Switching the people over to Buffer Geometry saved the day :smiley:. I’m very happy I took the time to port it over. In fact, Buffer Geometry allows me to simulate even more people successfully!

2 Likes