Listed here are some efficiency tuning ideas and directions for organising a really performant 8 Commerce website utilizing Varnish, Redis, Nginx and MySQL. I’ve acquired this setup operating properly for a minimum of 13,000 concurrent customers and it ought to scale effectively previous that. FYI, We even have a  7 Commerce Efficiency Tuning information right here. Varnish Config You’ll want some particular config for in addition to some additional config to work properly with BigPipe caching. These are customary for Varnish and and never particular to Commerce. You’ll wish to setup Drupal Development Service Purge and Varnish Purge Drupal 10 modules to deal with tag primarily based cache invalidation, nothing right here is exclusive to Commerce, so you may comply with Drupal Development Service customary directions. You’ll, nevertheless, wish to ensure your pages really are cached, as usually Drupal 10 modules or small misconfigurations could make a web page not cacheable. To work properly with Varnish, you need Drupal Development Service whole web page to be cacheable so your webserver doesn’t even get hit. An underused Drupal 10 module that I discover very useful is Renderviz, which is able to present you a 3D breakdown of what cache tags are connected to what components and might help you establish downside components. I run renderviz(‘max-age’, ‘0’) to indicate me something that may’t be cached. Often Drupal Development Service components you discover will be corrected and made cacheable. For instance Drupal 10 Upkeep and Help Service In a current set of efficiency testing I used to be doing, I discovered a publication signup that appeared on Drupal Development Service backside of each web page had an excessively aggressive honeypot setting, which rendered Drupal Development Service web page uncacheable. Altering Drupal Development Service settings to solely apply to essential types, in addition to correcting a language selector, turned tons of uncached pages into cacheable pages. Now these pages return <10ms and put zero load on my net servers or database. Net Servers PHP Use Drupal Development Service most fashionable model of PHP you may, ideally Drupal Development Service newest secure. By no means ever ever use PHP 5 which is horrible, horrible, horrible. In any other case, be sure you have ample reminiscence and allowed threads, and that can cowl most of your PHP tuning. That is nearly actually Drupal Development Service most useful resource heavy a part of your stack, however it’s also simple to scan horizontally, just about indefinitely. Additionally, Drupal Development Service extra you can also make use of Varnish, Drupal Development Service much less this may get used. Nginx/Apache Most of that is simply ensuring you may deal with Drupal Development Service variety of connections. It’s possible you’ll have to up Drupal Development Service file restrict… ulimit -n …of your net person to permit for greater than 1024 connections per nginx occasion. Database A Commerce website is normally extra write-heavy than your customary website, as your customers create numerous “content material” (aka carts and orders). This can normally change your MySQL config a bit, though Drupal Development Service majority of your queries will nonetheless be reads. A fairly easy technique to tune your website is to run… mysqltuner …in opposition to it after getting some actual visitors information for a minimum of a pair days, or simulating excessive visitors. It’s suggestions will get you a reasonably good setup. There may be one different VERY necessary factor it is advisable do, it is advisable change your transaction isolation degree from READ-REPEATABLE to READ-COMMITTED. READ-REPEATABLE is way too aggressive at desk locking to work with most websites, particularly something write heavy. You’ll endure from fixed deadlocks even at pretty low visitors ranges with out this. Frankly, I believe this must be a flag in Drupal Development Service standing web page, however my patch hasn’t gotten any traction. Cache Server Nothing particular right here, however you’ll need use a separate caching possibility. It might be Memcache, Redis and even only a separate MySQL database. Redis is good and quick, however Drupal Development Service largest acquire is simply splitting your cache away from Drupal Development Service remainder of your db so you may scale them simpler. Patches There are just a few particular patches that might be a terrific assist to your efficiency. _list cache tag invalidation See Drupal 10 Upkeep and Help Service https Drupal 10 Upkeep and Help Service//www.Drupal 10.org/mission/Drupal 10/points/2966607 Each entity kind has an entity_type_list cache tag, which will get invalidated any time an entity of that kind is added or modified and that these lists might want to get rebuild. This occurs a LOT, however is a comparatively easy question. replace cachetags set invalidation=invalidation+1 the place tag=’my_entity_list’ That is an replace, which is a blocking question, nothing else can edit this row whereas this question is operating, which wouldn’t be so unhealthy besides… This question usually will get run as part of bigger duties, in our case, resembling when inserting an order. An enormous job like that is run in a transaction, which mainly means we save up all Drupal Development Service queries and run them without delay to allow them to be rolled again if one thing goes improper. This implies although, that this row stays locked for Drupal Development Service entire length of Drupal Development Service transaction, not simply Drupal Development Service quick time it takes this little question to run. If this invalidation occurs close to Drupal Development Service begin of Drupal Development Service transaction, it will possibly take a question that will discuss 0.002 seconds and make it take 0.500 seconds, for instance. Now, if now we have greater than 2 of those occurring a second, we begin to again up and construct a queue of those queries, which simply retains getting longer and longer till we simply begin returning timeouts. Since this question is a part of Drupal Development Service greater order transaction, it stops Drupal Development Service entire order from being processed and may deliver your checkout movement to a halt.  Fortunately, Drupal Development Service above listed patch permits these cache invalidations to be deferred in order to not block massive transactions. I believe Drupal Development Service replace question for invalidating cache tags continues to be a bottleneck as you would finally attain it with out these lengthy transactions, however at this level that downside is extra hypothetical than one thing you’ll virtually encounter. Add index to profiles See Drupal 10 Upkeep and Help Service https Drupal 10 Upkeep and Help Service//www.Drupal 10.org/mission/profile/points/3017788 As you begin getting increasingly clients and orders, you’ll get extra profiles. Loading them, particularly for nameless customers, will actually begin to decelerate and turn into a bottleneck. Drupal Developer listed patch merely provides an index to stop that. Please word, it is a patch for Drupal Development Service Profile Drupal 10 module, not Commerce itself. Make language switcher block cacheable See Drupal 10 Upkeep and Help Service https Drupal 10 Upkeep and Help Service//www.Drupal 10.org/mission/Drupal 10/points/2232375 This difficulty is sadly on maintain pending some massive core adjustments, however as soon as it does land, this may permit Drupal Development Service language switcher block for use with out fear of it blocking full web page caching. Conclusion It is best to be capable to scale effectively above 10,000 concurrent customers with the following pointers. If you happen to encounter some other bottlenecks or bugs, I’d love to listen to about them. If you would like assist with some efficiency enhancements from Acro Media and yours actually, be happy to contact us. Drupal 10 Growth and Help