{
  "id": 1680677,
  "title": "Magento 2 Sales Order Performance: Grid Indexing, Order Loading & Bulk Operations",
  "url": "https://urgent.news/2026/08/18/magento-2-sales-order-performance-grid-indexing-order-loading-bulk",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-18T09:01:57.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/magevanta/magento-2-sales-order-performance-grid-indexing-order-loading-bulk-operations-ka1"
  },
  "original_language": "en",
  "account": "Most Magento 2 performance articles focus on the storefront, but the backend order management can suffer just as much when a shop grows past a few thousand orders. The sales order grid slows down, order view pages take seconds to load, exports time out, and customer service teams wait on screens instead of helping customers. This guide identifies the three biggest order-management bottlenecks in Magento 2 and provides solutions for each.\n\nMagento 2 stores order data across multiple tables, with the sales_order_grid table being the key for fast grid rendering. The sales_grid_order_indexer, dedicated to maintaining the grid, runs every time an order changes, leading to thousands of reindex operations per day on busy shops. Three issues commonly arise: the indexer running synchronously, an aggressive cron schedule, and comment updates causing frequent grid reindexes.\n\nTo address these issues, switch all sales grid indexers to Update by Schedule mode, adjust the cron schedule to run every 5–15 minutes, and limit comments to essential updates. Additionally, orphaned rows in the sales_order_grid table accumulate over time, causing performance degradation. Diagnose orphaned rows using the provided SQL query and remove them using the magerun2 command or manual deletion after a backup. For shops with millions of orders, consider archiving old orders using the built-in Sales Archive feature and implementing table partitioning on the created_at field to improve query performance. Lastly, the N+1 order loading issue, where related entities are loaded lazily and cause numerous queries, can be found by enabling SQL logging or profiling on the admin order page. Identify and optimize these issues to improve the performance of Magento 2's order management system.",
  "summary": "Most Magento 2 performance articles focus on the storefront — caching, Varnish, product pages. But there's a second performance front that hurts just as much: the backend order management . When your shop grows past a few thousand orders, the sales order grid slows down, the order view page takes seconds to load, exports time out, and your customer service team starts waiting on screens instead…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}