WooCommerce Admin is a feature plugin for WooCommerce, which uses React and the Gutenberg block editor to improve certain lacking core features, such as reporting and analytics in WooCommerce.
Reporting in WooCommerce can be slow, as well as being MySQL resource heavy if you have high order levels on the site, whilst the WooCommerce Admin is a step in the right direction. Though the WooCommerce Admin has been in development for a number of months, the feature plugin is still a beta plugin, and still not suitable for use on a live site.
In the most recent release of WooCommerce, which was version 3.6.4, it added a reminder nag, which is dismissible to install the WooCommerce admin plugin. The difference is that on the actual product page, it more clearly states that the plugin should be tested on a staging or dev site.
Once again: This plugin is under active development and, as such, we advise you to first install WooCommerce Admin in a staging/test environment. While this code is being run in production on sites, we recommend you first verify it works for you in a test environment, the same as any plugin for WooCommerce.
The WooCommerce Admin plugin on your live site can present a number of issues, ranging from the data in the report not being accurate, to more major issues of the plugin causing the site to act like it is DDoS itself. The DDoS like issue can mean your site server CPU usage will spike, as well as kill MySQL on the site server. The high number of requests to the WooCommerce REST API endpoint will cause CPU usage to spike.
The WooCommerce REST API requests look like this if you looked in the access log of the site server.
If you were using the WooCommerce Admin plugin on one of your child sites, the database table created by the plugin will not be deleted on deactivation. The custom database table in question is called
wp_wc_order_stats. You can delete (drop) that database table using phpMyAdmin.
Remember that this plugin is in development, and should not be used on a live site until it is stable unless you want to deal with your child site running into CPU spikes and it causing major performance issues.