[Bug] (k8s and vm) long load time between clicking the "Create Demo" button and going to the install progress prage

Open, Needs TriagePublic

Actions

Testing on my local setup vs production:

jhuneidi opened https://gitlab.wikimedia.org/repos/qte/catalyst/patchdemo/-/merge_requests/73

Make pages with streaming load faster

I'm wondering if flush() directly in the code (yes it will make it uglier) can make the page start to render earlier? It seems like it's still a lot of time before the browser starts to consider to render the page and I'm thinking that is because the server holds the on to the data? Is our backend server serve HTTP2?

Else I would look so that not the nginx in front of the server is the one that waits for the content and then delay things to the browser?

I think the 206 HTTP header is more used if you push a large file and part of its is downloaded?

jhuneidi merged https://gitlab.wikimedia.org/repos/qte/catalyst/patchdemo/-/merge_requests/73

Make pages with streaming load faster

@Peter Thanks for the suggestion! ob_implicit_flush is set to true already and we also tried adding flush() in the code but it didn't make a difference.

I wasn't sure about the 206 header either but we tested the change on our staging cluster and now have deployed to production. I think it is because we want to render the page before the new.php code has run to completion.

Finally there is no wait for page load!