Performance regression between 1.113 and 1.114

[javagl]

There seems to be a performance regression in 1.114 compared to the previous version.

What I tested with 1.113 and 1.114:

• Run npm run start locally
• Open the "OSM Buildings" Sandcastle on localhost
• Add viewer.scene.debugShowFramesPerSecond = true; to show the FPS
• Zoom in and out a bit with the mouse wheel.

With 1.113, the FPS remains basically constant at 59.
With 1.114, the FPS drops to 4 ... 10 while zooming. (When not zooming, it goes back to 59)

This is apparently related to the new Screen Space Controller behavior that was implemented with #11581 . When creating the OSM buildings tileset with

const osmBuildingsTileset = await Cesium.createOsmBuildingsAsync({
  disableCollision: true
});

then the FPS remains 59 even with version 1.114.

(I have not yet extensively tested it with other tilesets. Things like the Google P3DT do not seem to be affected so noticably, although a dedicated analysis (whether ~"the average FPS dropped by 5%" or so) could be difficult...)

---

EDIT: This might be one of the few cases where some system information might be relevant (at least more than in other cases). This was tested on Windows 10, with an NVIDIA GeForce RTX 2070, on the latest Chrome and FireFox.

[jjspace]

Possibly related to #11787

[ggetz]

I'm looking at this now. Basically, we were using bounding spheres rather than the bounding volumes to pre-optimize picking on tilesets. I'm working on the ray volume intersection logic and will have a PR open soon.