- Issue created by @nod_
I was curious about the test failures in BigPipeRegressionTest, and I think a large contributing factor is that using load events instead of the mutation observer causes the page to load much more slowly.
Not scientific, but on my local ddev with standard profile and the big_pipe_regression_test module installed:
- On HEAD, load time for
/big_pipe_test_multiple_replacementswas roughly 1m 13 sec - On the MR branch, load time for
/big_pipe_test_multiple_replacementswas roughly 14m 06 sec
I think this is happening because event handling is synchronous and blocking, while the mutation observer works asynchronously.
- On HEAD, load time for
- 🇫🇷France nod_ Lille
I profiled the change and this is a terrible, terrible idea. it's 10x slower and uses 10x the memory.