After beeing able to render my nodes to an variable (Render node to variable - works great in general) my controller actions are becoming slower and slower (because the document is getting bigger and bigger). Until now I didn’t find a way on howto render a view using a Command Controller. This would be the most elegant way because I could use queuing services, but I tried a lot without sucess.
However, I now decided to run those background tasks after the (visible) controller results have been flushed to the user and to wait for the PDFs to become ready with a Java Script that triggers a RestController. All of this works, but I’m not able to flush the output to the user.
Ends up in a white page being flushed to the user.
You might want to go full async processing for something like that and use e.g. the jobqueue package to send work to a background worker process. Less working against the technology, more robust/scalable handling and truly async.
I’m currently using “OutOfBandRendering” (https://github.com/ttreeagency/OutOfBandRendering) to render round about 400 nodes into a HTML file. I don’t know how to initialize a view in a CommandController (to be able to call $this->view). The only way I know would be to use a CommandController to call a ActionController via curl/wget. Or is there another way?
You can use the StandaloneView to be able to render templates from outside the Web MVC stack. You maybe need to provide it with a useful ActionRequest (referencing a useful faked HttpRequest) to properly resolve absolute URLs in the template. But for a first step and testing, you can just create a new StandaloneView() and then set the template and render.
However, it seems as if it’s some slower than calling the same functions via ActionController by about 25%. Is this possible or might there be a problem with my implementation? I’ve disabled caches completly to be sure that’s not a caching issue.
25% sounds a bit much. How and what exactly did you measure? There’s a bit overhead creating a new php process and bootstrapping Flow to render a node async, but if you work multiple jobs with one call that can be alleviated. Glad you got things working, that’s the first step. Optimization comes on top