WP All Import Pro: 10,000-product import and update benchmark
WP All Import Pro 5.0.6 took 381.098 seconds to import 10,000 WooCommerce products and 538.577 seconds to apply the matching update. Super Speedy Imports Pro 2.86.0 completed the same jobs in 12.950 and 16.450 seconds. That made Super Speedy Imports 29.428 times faster on the initial import and 32.740 times faster on the update.
The update is the more representative recurring job. It changed 2,500 existing products, added 1,000 and removed the 1,000 products omitted from the previous import file. Both importers produced the intended final catalogue of 10,000 published products.
Results for store owners
| Operation | WP All Import Pro | Super Speedy Imports | Difference | Verified result |
|---|---|---|---|---|
| Initial 10,000-product import | 381.098 s (6m 21.098s) | 12.950 s | 29.428 times faster | 10,000 products, categories, brands and two global attributes |
| 10,000-row update | 538.577 s (8m 58.577s) | 16.450 s | 32.740 times faster | 2,500 changed, 1,000 added, 1,000 omitted originals removed |
Migration and configuration
The input was a WebToffee-format CSV, not a file prepared for Super Speedy Imports. WP All Import was configured to map the product name, description, excerpt, prices, weight, SKU, product categories, brands and the global Colour and Size attributes. It processed 100 records per request and matched updates by SKU.
Super Speedy Imports recognised the WebToffee headers automatically. That is the practical migration benefit: the same supplier or export file can move across without rebuilding it in a Super Speedy Imports-specific format.
Page response while the imports ran
The deterministic collector repeatedly requested the home page as an anonymous visitor and wp-admin as a logged-in administrator before, during and after each import. These are average browser TTFB values.
| Run | Audience | Before | During | After |
|---|---|---|---|---|
| WP All Import initial | Visitor | 134.58 ms | 180.33 ms | 187.16 ms |
| Super Speedy Imports initial | Visitor | 120.26 ms | 144.53 ms | 106.24 ms |
| WP All Import initial | wp-admin | 125.08 ms | 172.85 ms | 314.22 ms |
| Super Speedy Imports initial | wp-admin | 130.76 ms | 293.55 ms | 153.46 ms |
| WP All Import update | Visitor | 132.24 ms | 151.42 ms | 124.06 ms |
| Super Speedy Imports update | Visitor | 138.32 ms | 127.19 ms | 125.12 ms |
| WP All Import update | wp-admin | 139.14 ms | 161.99 ms | 266.50 ms |
| Super Speedy Imports update | wp-admin | 131.58 ms | 200.66 ms | 129.64 ms |
The Super Speedy Imports runs were only 12.950 and 16.450 seconds long, so their during windows contain fewer samples and isolated spikes have more influence. The reliable operational difference is how long each server remains under import load.
Measured server impact
Average and maximum figures below come from Netdata during the timed import window. Cumulative CPU, disk-busy time and writes are calculated after subtracting the measured pre-import baseline.
| Run | CPU avg / max | RAM avg / max | Disk busy avg / max | Cumulative CPU | Cumulative disk busy | Cumulative writes |
|---|---|---|---|---|---|---|
| WP All Import initial | 28.75% / 60.45% | 1,193.2 / 1,324.6 MiB | 15.62% / 41% | 6.5718 vCPU-min | 59.513 s | 626.823 MiB |
| Super Speedy Imports initial | 42.29% / 74.54% | 1,242.4 / 1,303.7 MiB | 19.43% / 55% | 0.3404 vCPU-min | 2.516 s | 197.129 MiB |
| WP All Import update | 28.55% / 55.30% | 1,235.0 / 1,371.2 MiB | 16.35% / 42% | 9.1564 vCPU-min | 88.071 s | 834.875 MiB |
| Super Speedy Imports update | 43.51% / 66.14% | 956.7 / 1,041.0 MiB | 8.82% / 52% | 0.4346 vCPU-min | 1.441 s | 162.782 MiB |
A high instantaneous percentage is not the same as high cumulative usage. Super Speedy Imports used the server hard for seconds, then released it. WP All Import used a lower average CPU percentage but held CPU and disk resources for several minutes.
What this means for a managed host
The following projection models one initial import plus 364 daily updates on one domain. It applies the measured baseline-adjusted resource use from these runs. It is a capacity model, not a claim that every hosting bill will fall by the same amount.
| Annual resource per domain | WP All Import Pro | Super Speedy Imports | Saved |
|---|---|---|---|
| CPU | 55.659 vCPU-hours | 2.642 vCPU-hours | 53.016 vCPU-hours |
| Disk busy | 8.921 hours | 0.146 hours | 8.775 hours |
| Disk writes | 297.384 GiB | 58.056 GiB | 239.328 GiB |
For a fleet of 1,000 domains running this update daily, the measured CPU difference is equivalent to 3.028 of these four-vCPU servers when each server is budgeted to 50% sustained CPU. At an illustrative €35.49 per server per month, that is €107.48 per month or €1,289.74 per year of capacity. If the fleet has spare capacity already, the benefit appears as headroom and reduced contention rather than an immediate cash saving.
Method and versions
- Server: four AMD EPYC-Genoa vCPUs, 8.12 GB RAM and SSD storage.
- Stack: WordPress 7.0.3, WooCommerce 11.0.0, PHP 8.2.33 and MariaDB 10.11.18.
- Importers: WP All Import Pro 5.0.6 with WooCommerce add-on 4.0.6; Super Speedy Imports Pro 2.86.0.
- Dataset: the identical 10,000-row WebToffee-format CSV for both importers, with no images.
- Correctness: product counts, unique SKUs, descriptions, excerpts, categories, brands, colours and sizes were checked after completion.
Reproduce and inspect the data
The reproduction ZIP contains the exact CSV files, all six scenarios, effective configurations, environment and software inventories, a guide and checksums. It contains no plugin packages. You can also inspect the compact result JSON and readable data report.
For the full field, see WebToffee vs WP All Import Pro vs Super Speedy Imports.
Comments