We run some high volume Drupal Commerce sites, taking upwards of 10,000 orders an hour and have done a lot of performance work to get theseÂ values. Commerce traditionally can't be cached and tuned the same way an unauthenticated content site can, and normal tricks like varnish and other static caching are of limited use.
An overview of performance problems with Drupal Commerce and Drupal 7 and ways to fix or mitigate them.
Caching with authenticated users
Caching with dynamic content
PHP 7 benefits specific to Commerce
Scaling Attributes and Options
I will also touch on changes coming with Commerce 2.x for Drupal 8 and how this will affect performance in Drupal, especially related to cache contexts and bigpipe.
After this talk, Commerce site admins should be able to increase there order throughput hopefully by a factor or 3x or more, depending what there existing site setup is.
Blog post example regarding locking in commerce:Â https://www.acromediainc.com/blog/drupal-commerce-performance-locking
Led Digital Marketing Efforts of Top 500 e-Retailers.
Worked with Top Brands at Leading Agencies.
Successfully Managed Over $50 million in Digital Ad Spend.
Developed Strategies and Processes that Enabled Brands to Grow During an Economic Downturn.
Taught Advanced Internet Marketing Strategies at the graduate level.
Your Cart 0
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your IT knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.