There are multiple resources available to improve Magento 2 performance and all of them are pretty well documented.
Mode: Magento 2 has introduced modes, being the default one the slowest. Give the developer mode a try and always run your live store in production mode. More info here.
Cache: Varnish is supported out of the box, pretty easy to configure and ...
Magento runs reasonably well even in developer mode. It does need some initial configuration though.
First make sure Magento is set up correctly, assuming your on Ubuntu:
Use the latest build as Magento 2.2+ supports php 7.1
sudo apt-get install php7.1 php7.1-imap php7.1-xml php7.1-...
Magento is exceptionally fast as standard, it will load pages in 0.5s with all caches off and 0.2s with all caches on.
So you don't need strictly to make make Magento faster, you need to remove/change whatever is making it slow.
There's 2 bottlenecks for performance.
Addressing those is superbly simple,
Use a hosting provider that ...
I think that is not the right format for the cache nodes. My understanding is that all the cache settings should be nested inside the <cache> node. So to use two-level cache with memcached + database it would be something like this:
Editing directly in Magento with 300000 products will be slow on the Community Edition. This because with every save the indexer has to spin up and has to update the indexes. Unfortunately the indexers do not scale well beyond 100k in the CE version.
If you are running on Magento Enterprise Edition you have better indexers that will give you much better ...
No, it will slow down the site at least for a while, until the cache is warmed up again, because no content can be fetched from cache and all content has to be generated from database and XML files again.
As an example, opening a product page after flushing the cache often takes several seconds. The second time when everything is cached, it's typically down ...
The best guide that I could find is: https://www.nbs-system.co.uk/blog-2/magento-optimization-howto-en.html
Two-level caching is widely used in computing. Basically it is about having a small, but fast cache that is used for the first lookup, and if the data cannot be found in the first level it will be looked up in another cache that's ...
Reason for Slow
It is in developer mode with CSS/JS merge/bundle/minify enabled.
It is running on slow hardware.
Some 3rd party extension breaks performance.
SSD not used.
Full page cache and other caches are turned off.
PS: Here is how to find out what M2 mode you are in:
php bin/magento deploy:mode:show
When you are in Developer ...
I have the same issue after upgrade from 2.1.10 to 2.1.11.
The only thing that I've found now is a very slow Redis lib, it takes up to 99% of whole "Admin Login" action time. Make a note - not Redis service, but Redis php lib.
Code ref: Cm\RedisSession\Handler::read
Not sure about products saving, but I think it could be the same.
Hope this info will be ...
I had this problem too on a Macbook Pro (late 2016) with MAMP.
What I wanted to do was to create a Magento 2 theme. I had deactivated all caches and it took like 30s to reload a page (frontend and backend).
I activated all caches with the command "php magento cache:enable" and the site loads very fast. I can still work with Grunt and LESS without ...
Before migrating, I would consider contacting a 2nd hosting provider explaining the issue you have had. It is very rare to see the necessity of having a dedicated server. Your configurations are already very nice for the web. I would definitely listen a 2nd opinion from another provider. Good luck.
Can you provide more details like this is an ongoing issue or you started seeing it recently?
It is a fresh build or migration from M1 to M2?
How big is the catalog (products, categories)?
How many attributes a product has?
I would recommend to check (even as a trial option) solutions like:
Those tools will show you exact traces and timing of each separate PHP Trace that is involved within any operation/transaction (and allow you to find bottlenecks within Application / Database Flows)
On my installation it works pretty fast although I do not have many orders yet. But the query in the db I see in my code looks like this
SELECT `main_table`.* FROM `sales_order_grid` AS `main_table` WHERE (MATCH(`main_table`.increment_id,`main_table`.billing_name,`main_table`.shipping_name,`main_table`.shipping_address,`main_table`.billing_address,`...
Magento 2 is not slow by default. You have to follow these steps to make it fast:
Server and System Requirements
Update Magento Version
Enable Varnish Cache
Enable Flat Categories and Products
Content Delivery Network
Use lightweight theme
Images Should be Fully Optimized
I had this problem once. Turned out one of the installed extensions tried to "phone home" on each admin-page-load to a server that was no longer maintained - so the request this server had to time out before the actual admin page was rendered.
The extension I used back then was Robogento_RichSnippets.
I found this error by disabling all extensions in ...
The profiler acts like a tree, so when you read that CMS_Page takes 6 seconds, you need to look deeper down the list to find out which sub-elements slow down the page that much (you should look for about 0.3s on CMS pages).
Aoe made an extension that makes the Profiler much more "User Friendly", but it's a matter of preference. Here is the link if you want ...
Been there before with that data volume on the business side. So the first is your hosting and technical implementation for performance due to the indexing on save or reindex if direct database import. The second is the management and approval flow for product management.
The performance you need high quality architecture and preferably separate admin ...
For a catalog that size, you need to use some kind of mass-importer (Magmi or some Magento extensions). Doing it by hand seems impossible to me if you wanted them all imported relatively soon.
I don't quite understand what you mean " exporting the products out of that server into our live site." That doesn't seem very sound.
OK, I see you're ...