Ready to get started with WordPress VIP? Contact us
Showing page 13 of 17
Customers can self-launch a WordPress or a Node.js site from within the VIP Dashboard. Though launch tools in the VIP Dashboard differ for a WordPress single site, a WordPress multisite, and a Node.js site, all launches require the same preparation steps.
Versions of WordPress Core prior to 6.3 prime the term and/or meta caches after certain queries. This can result in performance issues and much longer than normal transaction times.
Enterprise Search automatically sends all standard front-end search queries to Elasticsearch. Non-standard queries can also be offloaded to Elasticsearch by adding custom code that modifies the behavior of WP_Query.
Performance issues can be caused by core WordPress queries that perform well when a site has a small amount of data, but as the volume of site content increases the queries require a longer amount of time to execute.
Analyzing a site’s performance, and making any necessary adjustments to improve it, will help to ensure a site’s performance during unexpected high traffic situations, including unpredictable types of request spikes. It can also improve a site’s performance during normal traffic patterns, and increase resiliency during expected high traffic events.
Rate limiting of Enterprise Search can occur if too many of the same queries are made directly to Elasticsearch (ES) rather than effectively utilizing caching.
Indexing compiles a site's content and inserts it into an Elasticsearch (ES) index. Indexing can be triggered with a VIP-CLI command.
Enterprise Search features such as facets, related posts, terms, and more can be enabled per site with custom WP-CLI commands run with VIP-CLI.
Post meta is not indexed by default. If post meta is not explicitly defined in the allow list, it will not be indexed.
Similar to post types, any registered taxonomy that is public will be indexed by default.