Run the load tests on Postgres, as production runs #139

Closed
opened 2026-10-05 10:38:09 -07:00 by rays · 1 comment
Owner

The load tests (#133) run their scratch daemon on SQLite, so their numbers carry SQLite's one connection (#136) and its locking, not what production sees on Postgres 18. The harness wipes its SQLite files before each run; on Postgres it would need a database of its own, emptied first (a throwaway container, or DROP SCHEMA public CASCADE), and a way to reach it from wherever the tests run.

The load tests (#133) run their scratch daemon on SQLite, so their numbers carry SQLite's one connection (#136) and its locking, not what production sees on Postgres 18. The harness wipes its SQLite files before each run; on Postgres it would need a database of its own, emptied first (a throwaway container, or DROP SCHEMA public CASCADE), and a way to reach it from wherever the tests run.
rays added the enhancement label 2026-10-05 10:38:09 -07:00
Author
Owner

Done in bbdcbe2: node tests/load/run.js --postgres runs the daemon in IPX_TEST_DATABASE_URL (ipodderx_test on production's server, as ipodderx, in /src/.envrc from ipx.env), schema ipx_load made afresh each run, refusing any database not named *_test, with ANALYZE after seeding. Budgets are per database. All four pass on both. Running it found #140.

Done in bbdcbe2: node tests/load/run.js --postgres runs the daemon in IPX_TEST_DATABASE_URL (ipodderx_test on production's server, as ipodderx, in /src/.envrc from ipx.env), schema ipx_load made afresh each run, refusing any database not named *_test, with ANALYZE after seeding. Budgets are per database. All four pass on both. Running it found #140.
rays closed this issue 2026-10-05 11:33:01 -07:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: rays/ipx#139