Skip to content

Conversation

@Basster
Copy link
Contributor

@Basster Basster commented Jan 9, 2020

The container preload file will only be generated when both factories and class_loader are inline, so you need to set both parameters to true explicitly.

The container preload file will only be generated when both factories and class_loader are inline, so you need to set both parameters to `true` explicitly.
@javiereguiluz javiereguiluz added this to the 4.4 milestone Jan 12, 2020
javiereguiluz added a commit to javiereguiluz/symfony-docs that referenced this pull request Jan 12, 2020
This PR was merged into the 4.4 branch. Discussion ---------- Hint for generating container preload file The container preload file will only be generated when both factories and class_loader are inline, so you need to set both parameters to `true` explicitly. <!-- If your pull request fixes a BUG, use the oldest maintained branch that contains the bug (see https://symfony.com/roadmap for the list of maintained branches). If your pull request documents a NEW FEATURE, use the same Symfony branch where the feature was introduced (and `master` for features of unreleased versions). --> Commits ------- 0e6a885 Hint for generating container preload file
@javiereguiluz
Copy link
Member

@Basster nice improvement! I wasn't aware of this. Thanks and congrats on your first Symfony Docs contribution!

@javiereguiluz javiereguiluz merged commit 0e6a885 into symfony:4.4 Jan 12, 2020
@jrjohnson
Copy link
Contributor

@Basster / @javiereguiluz I'm not sure if this step is still necessary. Enabling / disabling these in my app doesn't seem to matter, the preload file is generated and performance isn't measurably different. I think maybe symfony/symfony#36193 caused this setting to no longer be necessary in 5.1?

I hesitate to create a PR though because I'm not sure what these options do exactly and why they may be needed in different environments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment