2meet-data-optimizer

wpdev/2meet-data-optimizer

Fork 0

Commit Graph

Author	SHA1	Message	Date
wpdev	754f904e3b	perf(2meet-data-optimizer): route status and date ordering to entity tables - TMDO_Post_Query_Router: when a group's post_status / post_date copies are ready and none is NULL (one index probe per group per request), a single-post-type search with explicit statuses and date ordering INNER JOINs the flat table, filters the copied status, orders by the copied post_date and skips GROUP BY. Otherwise the query keeps its old shape. - New posts_orderby filter; bench gains an `entity+copy` variant. - Bench (1M, with SQL_CALC_FOUND_ROWS): scenario 1 p95 3,739 -> 773 ms (p50 670 -> 770); scenario 2 p50 356 -> 448 ms. Without found-rows the same shape runs in 8 ms (PR-030). - Verify: core unit 659 / integration 471 green, phpcs clean - PR: PR-029	2026-09-26 01:41:07 +08:00
wpdev	d3b72bd1af	test(2meet-data-optimizer): add scale benchmark report (native vs hot vs entity) - Benchmark 7 scenarios at 100k vendors / 1M listings with SQL shaped like WP_Query, TMDO_Query_Router and TMDO_Post_Query_Router - Native meta_query takes 14-17s; flat tables bring searches to 0.3-0.6s - Hot table lacks an hp_vendor index (3.4s); entity lacks composite indexes Verify: TMDO_TEST_DB_NAME=wp_wpdo_bench php tests/bench/run.php --iterations=20 PR: PR-005	2026-09-25 21:29:58 +08:00
wpdev	8fc1dc1f1c	test(2meet-data-optimizer): add scale seeder for 100k vendors / 1M listings - Seed a HivePress-shaped dataset three ways (native meta, entity tables, hot table) with flat tables built by TMDO's own schema code - Refuse any database not named *_bench before the bootstrap connects; bootstrap now honours a pre-defined ABSPATH for the wp-admin stub - Full scale seeds 9.5M postmeta rows in 7m25s; 0 value mismatches Verify: TMDO_TEST_DB_NAME=wp_wpdo_bench php tests/bench/seed.php --vendors=100000 --listings=1000000; unit 600 OK, integration 416 OK PR: PR-004	2026-09-25 20:55:25 +08:00

Author

SHA1

Message

Date

wpdev

754f904e3b

perf(2meet-data-optimizer): route status and date ordering to entity tables

- TMDO_Post_Query_Router: when a group's post_status / post_date copies
  are ready and none is NULL (one index probe per group per request), a
  single-post-type search with explicit statuses and date ordering INNER
  JOINs the flat table, filters the copied status, orders by the copied
  post_date and skips GROUP BY. Otherwise the query keeps its old shape.
- New posts_orderby filter; bench gains an `entity+copy` variant.
- Bench (1M, with SQL_CALC_FOUND_ROWS): scenario 1 p95 3,739 -> 773 ms
  (p50 670 -> 770); scenario 2 p50 356 -> 448 ms. Without found-rows the
  same shape runs in 8 ms (PR-030).
- Verify: core unit 659 / integration 471 green, phpcs clean
- PR: PR-029

2026-09-26 01:41:07 +08:00

wpdev

d3b72bd1af

test(2meet-data-optimizer): add scale benchmark report (native vs hot vs entity)

- Benchmark 7 scenarios at 100k vendors / 1M listings with SQL shaped like
  WP_Query, TMDO_Query_Router and TMDO_Post_Query_Router
- Native meta_query takes 14-17s; flat tables bring searches to 0.3-0.6s
- Hot table lacks an hp_vendor index (3.4s); entity lacks composite indexes

Verify: TMDO_TEST_DB_NAME=wp_wpdo_bench php tests/bench/run.php --iterations=20
PR: PR-005

2026-09-25 21:29:58 +08:00

wpdev

8fc1dc1f1c

test(2meet-data-optimizer): add scale seeder for 100k vendors / 1M listings

- Seed a HivePress-shaped dataset three ways (native meta, entity tables,
  hot table) with flat tables built by TMDO's own schema code
- Refuse any database not named *_bench before the bootstrap connects;
  bootstrap now honours a pre-defined ABSPATH for the wp-admin stub
- Full scale seeds 9.5M postmeta rows in 7m25s; 0 value mismatches

Verify: TMDO_TEST_DB_NAME=wp_wpdo_bench php tests/bench/seed.php
  --vendors=100000 --listings=1000000; unit 600 OK, integration 416 OK
PR: PR-004

2026-09-25 20:55:25 +08:00

3 Commits