Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[FrameworkBundle] Fix perf issue in CacheClearCommand::warmup()#23086

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
fabpot merged 1 commit intosymfony:2.7fromnicolas-grekas:warmup-perf
Jun 9, 2017

Conversation

@nicolas-grekas
Copy link
Member

@nicolas-grekasnicolas-grekas commentedJun 7, 2017
edited
Loading

QA
Branch?2.7
Bug fix?yes
New feature?no
BC breaks?no
Deprecations?no
Tests pass?yes
Fixed tickets-
LicenseMIT
Doc PR-

On slow file systems (eg on Windows), I noticed that writing files without doing any changes just kills perf.
Limiting the depth also helps when the symfony/cache component is used (because it can store thousands of files in its cache pool directory structure, and iterating there is also a waste offs time).
I choose the max depth by looking at where existing apps put their files and added one level more just in case.

@Wirone
Copy link
Contributor

This PR is related to my specific case where upgrading to 3.3 in one of our apps makes it unusable inapp_dev.php. I took Blackfire profile forbin/console cache:clear and it took 1m47s. After applying this patch it took 54s.

@nicolas-grekas can view those profiles.

@Wirone
Copy link
Contributor

Without additionaldepth limitations it took 1m8s.

@fabpot
Copy link
Member

Thank you@nicolas-grekas.

@fabpotfabpot merged commitb58f060 intosymfony:2.7Jun 9, 2017
fabpot added a commit that referenced this pull requestJun 9, 2017
…mup() (nicolas-grekas)This PR was merged into the 2.7 branch.Discussion----------[FrameworkBundle] Fix perf issue in CacheClearCommand::warmup()| Q             | A| ------------- | ---| Branch?       | 2.7| Bug fix?      | yes| New feature?  | no| BC breaks?    | no| Deprecations? | no| Tests pass?   | yes| Fixed tickets | -| License       | MIT| Doc PR        | -On slow file systems (eg on Windows), I noticed that writing files without doing any changes just kills perf.Limiting the depth also helps when the symfony/cache component is used (because it can store thousands of files in its cache pool directory structure, and iterating there is also a waste of *fs* time).I choose the max depth by looking at where existing apps put their files and added one level more just in case.Commits-------b58f060 [FrameworkBundle] Fix perf issue in CacheClearCommand::warmup()
This was referencedJul 3, 2017
@nicolas-grekasnicolas-grekas deleted the warmup-perf branchJuly 10, 2017 15:58
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

@fabpotfabpotfabpot approved these changes

Assignees

No one assigned

Projects

None yet

Milestone

2.7

Development

Successfully merging this pull request may close these issues.

4 participants

@nicolas-grekas@Wirone@fabpot@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp