How intensively does RmlUi allocate (and can it be controlled)?

[daniilrozanov]

Does RmlUi allocate memory from the heap (and for everything else) for each element in the DOM? Or does he have his own pool? Have you had any thoughts/benchmarks on how much this affects performance? Is there any plans to support custom allocators in the std style, or is it not necessary?

PS. A little context about my case. Although you don't need to delve into it, you may have had a similar experience. I plan to build a text editing window that supports syntax highlighting and preview mode (for example, switching from markdown source code to a nice-looking view). Frequent text changes are expected when printing, pasting, and deleting. Not only the text changes, but also the highlighting, so frequent recalculation of the entire subtree with text elements will be required. The amount of data may vary. Could this be a bottleneck?

[mikke89]

I wouldn't really worry too much about memory allocation per se. It is certainly part of the performance picture, but far from the only thing. Rather, I'd encourage you to think of the performance profile more widely. Since you are doing a text editor, I'm sure you'll meet some constraints that other users haven't, and thus might find some bottlenecks we haven't encountered before. It's really a matter of figuring things out as you go, and then tackling those. If you have a general worry, then you can do some prototyping and measure heavy (performance-wise) use cases close to what you might encounter.

It's a lot easier and more productive to talk about performance with concrete scenarios and numbers. Be sure to keep us in the loop though, sounds like a very interesting application!