2meet-data-optimizer

wpdev/2meet-data-optimizer

Fork 0

Commit Graph

Author	SHA1	Message	Date
wpdev	65c75dfc8d	feat(2meet-data-optimizer): support composite indexes on entity groups - register_group() accepts $args['indexes'] (name => ordered keys); indexes on unknown keys are dropped. Kept outside the field definition, so schema hashes are unchanged. - Schema_Manager::ensure_group_indexes() adds missing cidx_* indexes to the existing flat table in place; the applied definition is remembered in tmdo_entity_indexes so later requests skip SHOW INDEX. - Bench (1M listings, scenario 2): Entity p50 337 ms -> 278 ms with (hp_verified, hp_price), on par with Hot (269 ms). - Verify: core unit 656 / integration 459 green, phpcs clean - PR: PR-027	2026-09-26 01:05:23 +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

Author

SHA1

Message

Date

wpdev

65c75dfc8d

feat(2meet-data-optimizer): support composite indexes on entity groups

- register_group() accepts $args['indexes'] (name => ordered keys); indexes on
  unknown keys are dropped. Kept outside the field definition, so schema
  hashes are unchanged.
- Schema_Manager::ensure_group_indexes() adds missing cidx_* indexes to the
  existing flat table in place; the applied definition is remembered in
  tmdo_entity_indexes so later requests skip SHOW INDEX.
- Bench (1M listings, scenario 2): Entity p50 337 ms -> 278 ms with
  (hp_verified, hp_price), on par with Hot (269 ms).
- Verify: core unit 656 / integration 459 green, phpcs clean
- PR: PR-027

2026-09-26 01:05:23 +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

2 Commits