10 fps drop between big babylon versions

Bugs
1

it’s a separate thread which is started in No Possibility to create gpu particle system via node particle editor - #17 by TooCalm but it seems it’s a different issue. To address that i started new topic.

I created PG similar to PG which was created for particle issue. this PG has much meshes.

when i switch between 7.54.2 and 8.51.1 i have next results.

7.54.2 has 100 fps(maximum which i got)

8.51.1 has 90 fps(maximum which i got)

could you please check how much you have? it has exactly 10 fps drop like i have in my scene

No Possibility to create gpu particle system via node particle editor
2

I increased 1000 on Line 22 to 5000to get under the max FPS for my computer

I see 20-21 FPS on both 7.54.2 and latest on Mac Chrome

3

please try multiple times. For me it’s sometimes shows different values. my values it’s a highest values I saw

4

I also see a difference

  • 7.54.2: 120 (minimum) 170 fps (maximum)
  • 8.51.1: 90 (minimum) 108 fps (maximum)
    So the difference for me is more between 30 < 60 frames per second.

On the other hand the fps, no Absolut I’m at 60 fps whatever the version

5

On my side, fps is 60, absolute is :

  • 7.54.2 : 190 fps
  • 8.51.1 : 130 fps
7

Can you test with this PG?

You may have to change the number of spheres line 99, depending on your system.

This cancels out a change that could explain the difference (but on my system, I don’t see any difference).

8

changed to 1k spheres.

7.54.2 have 88 fps

8.51.2 have 83 fps

windows/opera/nvidia

i test with next steps:

run pg, wait 10 sec, check highest possible fps i see

do 10 times for each version, result above its a highest fps for 10 runs

i do 10 times because there is fluctuations in fps. some runs have 83 highest fps in 7.54 version some runs have 88 and 77 for 8.51 etc, also i reduce number of spheres because 5k spheres have 22 fps and its hard to see difference between versions

9

I tried with the 5000 spheres :

  • 7.54.2 have 35 fps
  • 8.51.2 have 22 fps

With 1000 spheres : (Because 5000 is too heavy)

  • 7.54.2 have 140 < 160 fps (max)
  • 8.51.2 have 110 < 125 fps (max)
10

Do you use inspector v1 to look at the absolute fps (add ?inspectorv1 in the url)?

I have 30fps difference between inspector v1 & v2 on this PG (with 2000 spheres): 80fps vs 110fps.

Latest Babylon version with inspector v2: https://playground.babylonjs.com/#CN4B58#13
Latest Babylon version with inspector v1: https://playground.babylonjs.com/?inspectorv1#CN4B58#13
Latest Babylon version with inspector v1 + improvements (?): https://playground.babylonjs.com/?inspectorv1#CN4B58#15
v7.54.2 (with inspector v1): https://playground.babylonjs.com/?version=7.54.2#CN4B58#13

cc @ryantrem for the perf difference between v1 & v2.

I took a snapshot in v1 and v2, and noticed that everything was slower in v2. So I thought that, for some reason, JS optimizations were disabled (or limited) when the v2 inspector was open. So I disabled JS optimizations (in chrome://settings/content/v8) and, after restarting Chrome, the absolute fps was similar in both cases (I had to reduce the number of spheres to 500 to get more than 60 frames per second): 90 frames per second ± 2 frames per second.

11

i don’t open inspector. i check fps in right bottom of screen

1 Like
12

This PR should improve performance:

1 Like
13

Yes, my tests, for my part, are done with the V2 inspector available by default with the playground.
I haven’t tried with inspector V1.

14

@TooCalm is it all good now ?

15

Hey, It’s hard to say. Fix was about inspector versions but i don’t use inspector for fps check i just use indicator in bottom right. Anyway i couldn’t get 100 fps on previous version but now i can so i think it became better.

But i noticed another thing. When i open PG i have ~100fps. But if i click play PG (not f5 page reload just PG button) i see 10-15 fps drop and it never recover to 100 fps no matter how many i try to play PG. It looks like there is some leak of resources. Do you have any thoughts?

1 Like
16

What PG(s) are you testing?

17

From the topic start. Babylon.js Playground

I’m not sure but maybe it’s related. From some last version (about 2-3 weeks ago) playgrounds started to open very slow. This PG which i linked is opening about 60 secs. But if i open it through VPN it opens much faster. I see errors in console about some timeouts

image
image2517×162 19.5 KB

I think PG opens too slow because of this timeouts. It waits until they fail and only then show PG. Through VPN no timeouts and it opens faster (about 10 secs) but I think it’s because of VPN. My friend from another country opens it very fast(2secs) but when he uses VPN it loads too slow.

I didn’t report this as it seems my local issue (maybe some country restrictions) and i think you will not fix it but maybe bug which i reported above can be related to this. If it’s so then i think i need to test it with inspector v1. Not sure if it’s possible as i can’t find any switcher to previous inspector.

18

I tried to reproduce your problem, but I couldn’t. I got about 90/92 frames per second the first time. I then clicked “Play” five times, waiting 10 seconds each time to let the frames per second stabilize, and I still got about 90/92 frames per second each time.

It looks like the problem comes from githack.com server, which is answering too slow.

You can force using v1 by adding inspectorv1 to the url:

19

with inspector v1 i still have this issue. 70fps→62fps. Then the only way is to have more tests. Maybe other people will try to test this case and send their results

20

Regarding rawcdn.githack.com it’s not answering slowly it’s blocked. If i try to open page it shows page that it’s restricted by my country

1 Like