What RowSprout costs when it is sitting still, and when it builds 200 pages

What RowSprout costs when it is sitting still, and when it builds 200 pages - MakeWPFast

Jeroen van Beusekom asked me to measure RowSprout the way I measure other plugins, and to generate a batch of pages while I was at it. I did that today. Free RowSprout 3.2 from WordPress.org, RowSprout Pro 3.2.2 on top.

The bench is a clean WordPress 6.9.4, PHP 8.3, MariaDB 10.11, GeneratePress. No Redis, no Memcached. TTFB is the median of five samples. A clean request already moved between 14 and 31 ms, so a few milliseconds is noise. The query count is the number I trust. Memory is PHP’s peak allocation, and it jumps in chunks. 0 KB means it stayed in the same bucket.

Sitting still, before any generated pages exist, the free plugin adds 10 queries on the front. Pro adds none on top of that. In wp-admin the free plugin adds 32 queries and 2 MB. Pro adds about 5 more queries there.

I then took the city-break sample that ships with the plugin, swapped the rows for 200 made-up cities, and left the batch size at the default of 40. Queuing took 0.75 seconds. Five queue runs built all 200 pages in 6.4 seconds. About 32 ms each. The placeholders were filled in. I checked one page: the title was “City break in City 001”, the body had the city, and no @code_ token was left behind.

Those 200 are the rowsprout_page post type. One of them, next to a normal page with the same content and both plugins still on, had the same TTFB (31 ms) and the same memory. The generated page ran 26 queries. The normal page ran 23.

The front of a generated page is a normal page plus 3 queries. The cost that shows up is building them.

I repeated the front with Redis after that, on the same site. Without Redis the gap was still 10: 18 queries with both plugins, 8 with them off. The fresh front that morning was 29 and 19. Same gap.

With Redis warm, the front was 6 queries with the plugins and 0 without. So 4 of the 10 go away. 6 stay. Those 6 are Action Scheduler checking action_scheduler/migration_hook on every front request, even when there is nothing to generate.

Get WordPress Performance Tips

Join developers and agency owners who get backend optimization strategies, tool releases, and deep-dive guides.

No spam. Unsubscribe anytime. I respect your privacy.