Make OptimizeCommand compile views

[anlutro]

Had this idea a while ago but dismissed it, but a request from the IRC channel reminded me of it. By making the artisan optimize command compile existing views (assuming they can be compiled) you can bring some load off your server or at the very least ensure that the first person to hit your website won't get a much slower response than the ones after him/her.

This is obviously not an issue for 99% of the framework's users, but I thought, why not?

[richardkmiller]

+1. If you run n web servers, then the first n hits of a given page take the compilation hit, assuming each web server is independent. Alternative 1 is a shared NFS mount or DRBD to share Blade templates across web servers, but that increases SPOFs and decreases robustness. Alternative 2 is to disable Blade template caching entirely (let it be generated on each page load) and assume that the file system cache and php5-fpm opcache will provide enough performance.

[Anahkiasen]

👍

[crynobone]

How would laravel then know the view is already available in compiled? We currently manage to do so with classes since the autoloader can use class_exists()

[anlutro]

The compiled path is simply an md5 of the real view path, so the framework will know just as it would if the view was compiled on request. https://github.com/laravel/framework/blob/v4.2.1/src/Illuminate/View/Compilers/Compiler.php#L34-L43