Magento – Tips and tricks for fast Magento2 localhost development

I'll have a guess:

How is your setting in System > Web > URL Options > Auto-Redirect? Is it "302", and if you set it to "301", does the behaviour change (to now being a 301 redirect?).

A few days ago, I had a similar issue when features just stopped to work. The issue was that the disk space of the server was full, so MySQL could not access enough tmp/-space for some queries. This resulted in pages wihout loaded product lists and the like. Maybe, your core_url_rerite table is immensely huge, so that it can not be read, and the setting mentioned above produces a 302.

You can use this vagrant box https://github.com/EcomDev/fast-hypernode.

I use it and it is quite fast. In developer mode with cache disabled and xdebug a page refresh is about 2-3 seconds.

Or you can use the vagrant box provided by magestead: http://www.magestead.com/

• use php7.
• use gulp for generating css and js (faster than grunt). You can try the already built configuration by snowdog (ready in 2 minutes): https://github.com/SnowdogApps/magento2-frontools
• use 3gb of ram if doing testing.
• disable only the cache that you need. If you're doing frontend you don't need to disable any cache.
• use livereload or browsersync for frontend development so that you don't need to reload pages.

Understand what magento commands do and when to run them. If you're running a lot of setup:static-content:deploy then you'll go mad seeing those dots. Grunt or gulp don't know about @magento_import so that's why when you add or remove files you need to run dev:source-theme:deploy which is much faster than the above one.

What doesn't improve:

Unless you have over 100k products redis makes no difference so don't bother (http://www.developers-paradise.com/wp-content/uploads/2016/05/05-Yaroslav-Rogoza-Magento-2-performance-comparison-in-different-environments.pdf).

Currently because of how magento2 uses requirejs (2mb of js), http2 makes no difference either.