{"id":19003958,"date":"2026-08-26T19:58:58","date_gmt":"2026-08-26T19:58:58","guid":{"rendered":"https:\/\/wordpress.org\/support\/topic\/working-well-with-a-large-database-46gb\/"},"modified":"2026-08-26T19:58:58","modified_gmt":"2026-08-26T19:58:58","slug":"working-well-with-a-large-database-46gb","status":"publish","type":"topic","link":"https:\/\/wordpress.org\/support\/topic\/working-well-with-a-large-database-46gb\/","title":{"rendered":"Working well with a large database (46GB)"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Using Index WP MySQL for Speed and setting innodb_buffer_pool_size = 4G seems to be working well<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Also using this snippet<br \/>\/\/ Restrict HPOS admin search to core fields to prevent full table scans on wp_wc_orders_meta<br \/>add_filter(\u2018woocommerce_hpos_admin_search_meta_keys\u2019, function($meta_keys) {<br \/>\/\/ Return an empty array or only essential custom meta keys you frequently search for<br \/>return array();<br \/>});<br \/>This keeps the scan narrow (indexed\/high-value keys only) instead of nuking meta search entirely and improves order search speed.<\/p>\n","protected":false},"template":"","class_list":["post-19003958","topic","type-topic","status-publish","hentry"],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19003958","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic"}],"about":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/types\/topic"}],"version-history":[{"count":0,"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/topic\/19003958\/revisions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/support\/wp-json\/wp\/v2\/media?parent=19003958"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}