Performance

[rolandschuetz]

I love the package and use it a lot. In a recent project, I had a performance problem and debugged rendering a few hours. In the end, it came down to Carbon.Link.

I prepared a test case while rendering a simple link tag 1000x took ~7.5 sec on my notebook in dev context, the Carbon.LInk version took ~30.5 sec. That difference is massive.

Not yet sure how to solve it, but I found it worth documenting it here.

Here's the test case

[rolandschuetz]

@jonnitto Why do you convert a node to an identifier (here) to then convert it to a not with ${Neos.Link.convertUriToObject(link, node)}?

And why do you handle the section logic yourself, instead of using the NodeUri?

[jonnitto]

Yeah, I know, I should refactor this. This will be a breaking one…

[rolandschuetz]

What was the original intention behind this?