Text demo only renders at 45fps due to slow per-frame layout about pathfinder HOT 4 CLOSED

The problem is that we have to lay out the atlas from frame to frame as glyphs enter and exit the view (because we don't render glyphs that are off screen). That means that we have to keep modifying uvs every frame, since glyphs may be at a different atlas rect each frame. This is the same kind of thing that WebRender has to do. Unfortunately, I have to do it in JavaScript, which is why it's slow…

There is probably a simpler solution that will work.

from pathfinder.

Interesting. Especially since the amount of text in the demo is a pretty small amount I would hope WebRender would be able to process in less than a millisecond. I know Javascript is slower than Rust but over 10x isn't what I would have expected for a modern JIT, does Webrender do something smarter that Pathfinder could do as well maybe? Or is it maybe something that making the JS use more linear typed arrays could help?

Although I imagine that CPU performance of the JS demo isn't considered super important since it's a demo, and while GPU performance is reflective of GPU performance in a real system, any real system would have a different CPU implementation.

from pathfinder.

Has the situation evolved now ?

from pathfinder.

No longer relevant with Pathfinder 3

from pathfinder.