Fat Object issue mentioned in Chronicles

Questions
1

David talked about object with numProperty > 128 will cause performance issue.
I wonder where I can get more info about it?
Through Inheritance, a class’ member can easily surpass 128.

2

There is an old blog post about that issue: My fat objects are slower than my thin ones | Eternalcoding

3

The value is not set in stone, Chrome/Edge specifc as well but trying to not go over is a really good thing :slight_smile:

4

they discuss a test that detects objects that have too many properties.

I looked for this test in the babylon source, but couldn’t find it.

Can someone tell me where to find it?

5

As far as is understand this is a test done by the Chrome browser (or its javascript engine) itself.

6

I mean the test that prevents the commit of objects with too many properties to the babylon source

7

Here it is Babylon.js/packages/dev/core/test/unit/Meshes/babylon.dictionaryMode.test.ts at master · BabylonJS/Babylon.js · GitHub

1 Like