I’m benchmarking BoundingInfoHelper on Chrome and Firefox against Seedborn stress test scene on dev under webgl2. The helper runs on a callback every frame for the animated farmhands only. Farmhands are clones with a materialPlugin. On average, each farmhand is <500 verts with about 50 bones. My code diff is:
new: await _this.game.BBHelper.computeAsync(_this.srcMesh);
old: _this.srcMesh.refreshBoundingInfo(true);
which is a one-liner change. I need to stress that there are no other edits, I only comment/uncomment to use 1 or the other. Below is the perf snapshot for v8.0.3.
I wait for the scene fps to stabilize somewhat b4 the screen capture. The control case is no BoundingInfoHelper, ie, the default refreshBoundingInfo(true). BoundingInfoHelper appears to be consistently worse across the 2 browsers for me. Maybe my use case isn’t the best use of the helper or the transformFeedback isn’t performant or other interactions causing the hit.
Not trying to diss the new stuff, I was looking forward to the perf gain. But shrugs…
Hope this helps.