Skip to content
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

why i disable all caches and enable xdebug that cause magento very slow? #1755

Closed
LifeAsBook opened this issue Aug 27, 2015 · 8 comments
Closed
Labels
Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed

Comments

@LifeAsBook
Copy link

No description provided.

@ooxi
Copy link

ooxi commented Aug 27, 2015

That's like asking why your car is slow if you remove all tires but add a heavily loaded trailer ;)

@dmitrii-fediuk
Copy link

XDebug slows PHP down in several (3-5-10, depends on a particular code) times, it is normal.

@LifeAsBook
Copy link
Author

@dfediuk Can you tell me a way to do efficient develop and to see the effect so as not to clear the cache every time

@buskamuza
Copy link
Contributor

@LifeAsBook , it depends on your developer flow. Could you, please, clarify what exactly you're modifying, so you need to cleanup cache all the time? Maybe you can disable just some specific parts of cache and still get benefits of other caches. What kind of files you often modify and need to refresh cache after it?

@LifeAsBook
Copy link
Author

@buskamuza thank you, you are beautiful! I do Implementing payment gateway in Magento 2 , what can i disable some specific parts?

@buskamuza
Copy link
Contributor

@LifeAsBook , sorry for the delay.
So, if you're developing a payment gateway, I would assume that you may go through different stages of the development, where different files are changed.

  1. You may change configuration files. In this case, I'd recommend to refresh "Configuration" cache type, when you want to see your changes. You may also disable this cache, but it may slow-down the application significantly, so it's better to just refresh the cache after the changes.
  2. When you work with layouts or templates, you may want to disable "Layouts" and "Blocks HTML output" cache types, as well as "Page Cache" type. When you're done, enable it back.
  3. When you work with the classes, you may keep all the cache types enabled, but you need to clean-up var/di and var/generation, if you change public interface of the classes or DI configuration (deeper understanding of how DI works in Magento may help to understand when you really need to clean it up and when not).
  4. If you work with JS, CSS, LESS files, you may also want to disable or refresh "View files fallback" and "View files pre-processing" cache types in case you add or remove these files. In case you modify LESS files, you may want to cleanup pub/static folder or switch to developer mode of the application (both ways lead to significant slow-down of the application). You may also use bin/magento dev:css:deploy CLI command to process specific LESS files (see the command's help for more information).

@LifeAsBook
Copy link
Author

@buskamuza thank you very much!i want you to be a friend

magento-team pushed a commit that referenced this issue Dec 4, 2017
[Kraken] Move EQP static tests to Magento core
@magento-engcom-team magento-engcom-team added the Fixed in 2.4.x The issue has been fixed in 2.4-develop branch label Aug 19, 2020
@magento-engcom-team
Copy link
Contributor

Hi @LifeAsBook. Thank you for your report.
The issue has been fixed in #29429 by @Nazar65 in 2.4-develop branch
Related commit(s):

The fix will be available with the upcoming 2.4.1 release.

@magento-engcom-team magento-engcom-team added the Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed label Aug 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Fixed in 2.4.x The issue has been fixed in 2.4-develop branch Issue: Format is not valid Gate 1 Failed. Automatic verification of issue format is failed
Projects
None yet
Development

No branches or pull requests

6 participants