Skip to content

Excessive Initialization time on 2.6.8 in dev environment #14768

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
jfx opened this issue May 28, 2015 · 7 comments
Closed

Excessive Initialization time on 2.6.8 in dev environment #14768

jfx opened this issue May 28, 2015 · 7 comments

Comments

@jfx
Copy link

jfx commented May 28, 2015

On Previous versions of symfony (lower than 2.6.8) the response time of a page was about 800 ms in dev environment. With the upgrade in 2.6.8 the response time was more than 4s with high usage of CPU. In production environment, I didn't notice any response time change between 2.6.7 and 2.6.8.
The timeline of the toolbar shows an Initialization time from 300ms for 2.6.7 to 3800ms for 2.6.8.
Environment :
Linux Ubuntu 15.04
PHP 5.5.9

@ewgRa
Copy link
Contributor

ewgRa commented May 28, 2015

I install fresh Symfony 2.6.8. Total time 59 ms for dev env and home page of demo.

Maybe cache? In dev env there is many checks about changes in configs and so on. When you change something - it need time to recreate configs, compile twig cache and so on. Try reload page twice.

Also it can be specific Bundle, or third-party soft or something like this. Try install fresh symfony and than step by step add your bundles and software that you use.

@chbruyand
Copy link
Contributor

Hello,

This seems to be introduced in pull request #14262.

Regards.

@rafalkrawiec
Copy link

Hi,

I also noticed this performance issue after udpdate to 2.6.8. In my application, after some tests I've found that using assetic controller is causing a big loss of performance.

In prod environment application works without problems because assetic controller is turned off, but in dev environment response time jumped from about 2000ms to over 9000ms and CPU usage is up to 100%. After turning off a controller it goes back to ~2000ms.

I've checked and the most time and resources are taken by container compilation and request matching (where routes collection are loaded and saved to cache), which are made for every request, also those for assets. Maybe this is specific for my application but in 2.6.7 version there was no such problems.

@Padam87
Copy link
Contributor

Padam87 commented May 28, 2015

#14771

@whisller
Copy link

Sadly I've noticed this problem on our projects as well. Needed to downgrade to 2.6.7.

@kniziol
Copy link

kniziol commented May 29, 2015

Same problem here. Only downgrade to 2.6.7 resolves the problem...

@jfx
Copy link
Author

jfx commented May 30, 2015

Hi,
With 2.6.9 the performance regression seems to be solved.
Thanks for your quick solution.

@jfx jfx closed this as completed May 30, 2015
fabpot added a commit that referenced this issue Jun 5, 2015
…ted (chbruyand)

This PR was squashed before being merged into the 2.8 branch (closes #14781).

Discussion
----------

[TwigBundle] Reconfigure twig paths when they are updated

| Q             | A
| ------------- | ---
| Bug fix?      | yes
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | yes
| Fixed tickets | #14771, #14768, #14262, #14778
| License       | MIT

Refresh twig paths upon creation and deletion. As we don't care neither about path's modification time nor path's content, a new Resource has been added in the Config Component.
Full discussion in #14778.

Commits
-------

3cbff05 [TwigBundle] Reconfigure twig paths when they are updated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants