wpsolr (elastic search index) compability

  • Resolved freshuk

    (@freshuk)


    1 year, 1 month ago

    hello,

    our website has around 150k orders in the database, 1k products, 30k users, 100k coupons and growing of course.

    database is around 10gb in size. we use redis object cache and wpsolr plugin with an elastic search live indexing for the heavy tables mentioned above (all the backend wp-admin data for orders, products, users and coupons is queries from the elastic search index).

    still, when 2-3 admin users display 300 orders on each page (must business requirement), there is some slowness.

    due to the data being queried from the elastic index (with help of the wpsolr plugin) and not from the database directly i wonder if we can benifit from your awesome plugin to tweak it even more.

    thank you

Viewing 1 replies (of 1 total)
  • Plugin Author OllieJones

    (@olliejones)

    Thanks for the question. I am not familiar with wpsolr, so I can’t offer a specific answer. I do know that the typical WordPress core search operation ends up hitting the database with a column LIKE '%searchterm%' query predicate. This plugin does nothing to optimize such predicates. They’re very hard to optimize without resorting to a different kind of search system like wpsolr or relevanssi.

    I can say that this plugin’s keys benefit the specific DBMS queries used by WooCommerce to display product pages, especially when the number of products is large.

    Big performance gains often come in queries involving JOINs of the wp_posts and wp_postmeta tables (also involving user and terms, and their meta tables).

Viewing 1 replies (of 1 total)
  • The topic ‘wpsolr (elastic search index) compability’ is closed to new replies.