magento2: Very BAD Performance with Magento 2 on Mac OS X

Hello

Im trying to figure out how to develop a custom theme with Magento 2 and its been a huge pain so far. I have developer mode set with

bin/magento deploy:mode:set developer

The problem is that Magento takes over a minute to load any page, its almost unusable. My system specs are

Mac OS X 10.11.2
Apache 2.4.16
PHP 5.6.16 - memory_limit: 2048M
MySQL 5.6

I installed PHP/MySQL locally to avoid the virtual setup but it seems the slow performance is about the same. Is there any tips to increase page load time when set to developer mode?

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Reactions: 3
  • Comments: 39 (15 by maintainers)

Commits related to this issue

Most upvoted comments

I think this ticket should be closed. Mac OS X isn’t listed as supported platforms of M2: http://devdocs.magento.com/guides/v2.0/install-gde/system-requirements.html

I have to strongly disagree a lot with the fact it seems people just say “Use Vagrant” - I don’t see that as a solution to yet another Magento performance problem running in deployment lifecycles. It has been by far the most underperforming application I have ever had the joy of working with.

I appreciate that there may be some issues with Docker and OSX’s file system, however Magento is the first project I have worked on where this actually seems to be noticeable to the naked eye.

Has there been much push for information on exactly what is causing such issues with Docker? - Not every team / org have the option to just chop and change from Docker to Vagrant. Over the years I have fallen out of love with Magento. It has become the Go-To E-Commerce platform, yet lacks any clear focus on performance. I for one no longer back the use of Magento for new clients, it has become quite honestly gross to work with. There are some really nice Python E-Commerce packages coming out which offer a much easier platform to work with, a performance based package which runs on 1/1000th of the cost Magento costs to run. This proves how much Mango needs to just be ditched and re-written, hopefully Adobe will do what they did to Fireworks and ditch it 😄

I have never in my life worked on anything which takes more than 10 seconds to load a page in development let alone the 1+ minutes to render a page which we see. The whole platform is stuck in the past.

Magento 2 just seems like a massive Sugar Coating Sh*t task. My 50 pence.

Have you disabled caching? What is the output of $ bin/magento cache:status? Being used to working with (some) disabled caches on Magento 1, it was a change I had to learn to live with when developing with Magento 2. Caching should practically never be disabled.

Also, is xdebug installed in your php? You can see by running php -m | grep xdebug. If that outputs xdebug it is installed. If so, make sure it is not enabled for every request automatically, but instead only on request. In the PHP settings, the value for xdebug.remote_autostart has to be set to Off and xdebug.remote_mode should be req.

+1 I also have this problem on my Mac.

@Vinai Never heard about Valet+. Sounds to be an incredible alternative to Mamp and has http/2 support. Thanks for the hint.

Try to enable opcache on Mamp but add/uncomment opcache.validate_timestamps=1 on your php.ini. This seems to be a good improvement.

Moving from mac to linux is out of discussion (at least for me).

I spent 2k+ USD for a MacPro 2018 with core i9 2.9 + 16Gb ram + 512 SSD After install magento 2 with PHP 7.1 + Apache 2.4 + MariaDB Default Magento + sample data Every page it sends 15-20 seconds to load.

x-debug not installed, opcache not installed.

CSS & JS not bundle, not merge

With Magento 1 it runs like fly but Magento 2 takes to much time to load a page.

How can I improve performance for my Mac or this MacPro has issue?

Everything else goes well with great speed, just Magento 2 NOT 😦

I am also developing in mac and it was very slow. Disabling JS/Css merging makes it faster.

I know this is closed, my apologizies for posting, but I did a “clean” composer install without sample data on OSX, it feels faster now. Also added local server name ::1 to etc/hosts not sure if has an affect but it was advised around.

Exactly @markoshust that’s why you should give this a try: https://github.com/paliarush/magento2-vagrant-for-developers This will allow you to develop on an OS supported by Magento without leaving the comfort of your own OS. However, I also use a LAMP stack on my mac using Macports which seems to be fast and reliable but this vagrant setup works on most systems.