Performance on scenes with large numbers of tiles significantly worse in v10

[Sky-Captain-13]

What happened?

Performance in scenes with admittedly excessive numbers of tiles is significantly worse in v10 than in prior versions of Foundry. In v9, toggling the visibility state of a single tile was near instant and multiple uses of a macro to trigger that state change could be done rapidly. In v10, triggering the macro multiple times in a row results in only parts of the targeted tiles changing visibility and the time it takes to change has increased by a factor of at least 10 to 15 (100 ms to 1500 ms).

What ways of accessing Foundry can you encounter this issue in?

• Native App (Electron)
• Chrome
• Firefox
• Safari
• Other

Reproduction Steps

1. Create a scene.
2. Add 6000 or more tiles.
3. Use a macro to toggle the visibility state of a tile.

What core version are you reporting this for?

Version 10 (build 283)

Relevant log output

const perf = Date.now()
await canvas.tiles.placeables[0].document.update({hidden: !canvas.tiles.placeables[0].document.hidden})
console.log("Compute time:", Date.now()-perf)
VM5172:3 Compute time: 1399
undefined
pixi.min.js:8 [Violation] 'requestAnimationFrame' handler took 213ms
const perf = Date.now()
await canvas.tiles.placeables[0].document.update({hidden: !canvas.tiles.placeables[0].document.hidden})
console.log("Compute time:", Date.now()-perf)
VM5177:3 Compute time: 1343
undefined
pixi.min.js:8 [Violation] 'requestAnimationFrame' handler took 236ms
const perf = Date.now()
await canvas.tiles.placeables[0].document.update({hidden: !canvas.tiles.placeables[0].document.hidden})
console.log("Compute time:", Date.now()-perf)
VM5182:3 Compute time: 1327
undefined
pixi.min.js:8 [Violation] 'requestAnimationFrame' handler took 218ms

Bug Checklist

• The issue occurs while all Modules are disabled