SolidParticleSystem memory limit

Questions
1

Hi!
I’m trying to visualize a bunch of particles. One million :smiley: Ok, the bunch was a joke. :smiley: But the browser breaks “Aw, Snap!” :smiley: at around 400k. Memory usage by chrome is at “only” 2.5 GB at this point. Is there anything I can do with this?

Thank you!

EDIT: Maybe I could create more SPS instances…

2

Not really, the browser limit per tab is not smthg you can change or influence :frowning:

3

Do you think it’s an out of memory issue?

4

yup sounds like it

5

The latest version of Google Chrome (desktop 64-bit version), ver 80.0, can handle up to 4GB of memory per tab as of April 2020.

So it should go higher. And the 2,5 was per Chrome instance.

6

check if you have 64 bit installed mine keeps switching between 32 and 64 for reasons… :slight_smile:

7

Version 95.0.4638.69 (Official Build) (64-bit)

I am going to try out something :vulcan_salute:

1 Like
8

Ok, so this is working, 800.000 particles but in separate systems. This opens up new questions, whether it’s really a memory issue?

    const spsCount = 80
    for (let i = 0; i < spsCount; i++) {
        const sps = new BABYLON.SolidParticleSystem("sp" + i, scene)
        sps.addShape(box, 10000)
        sps.buildMesh()
    }
9

might be a over the limit for one of the arrays or buffers only then :slight_smile:

10

NO no no… :smiley: I have a lot of code already written around SPS… and it seems I need to switch back to my beloved thin instances :smiley:

EDIT: or lower my expectations :smiley:

1 Like
11

It seems you are right! :muscle:
window.performance.memory.jsHeapSizeLimit give me only 2 Gigs

I’ve already checked the PointCloudSystem limit and it breaks around 3,4 mil of points but the absolute FPS is still at incredible:
image

:smiley:

2 Likes
13

This is looking cool!