Improve test stability by increasing MongoDB connection pool size

Update `replit.md` to document the increase of `MONGO_POOL_SIZE` from 2 to 5 in the test environment configuration to enhance stability during parallel test execution.

Replit-Commit-Author: Agent
Replit-Commit-Session-Id: 271f3cac-bab1-4e81-9982-f31b3b030aab
Replit-Commit-Checkpoint-Type: full_checkpoint
Replit-Commit-Event-Id: 260ef33f-bb92-40d0-82ef-652c94ce7f29
Replit-Commit-Screenshot-Url: https://storage.googleapis.com/screenshot-production-us-central1/7ea4278b-5c6c-4065-9cb8-f1013771318d/271f3cac-bab1-4e81-9982-f31b3b030aab/69H2O1r
Replit-Helium-Checkpoint-Created: true
This commit is contained in:
bewest
2026-01-19 23:02:42 +00:00
parent 65170b6b48
commit 875d8542c1
+1 -1
View File
@@ -40,7 +40,7 @@ The frontend utilizes Webpack for asset bundling and features charting with D3/j
To restore legacy behavior: `MONGO_POOL_SIZE=100`
Test environment uses `MONGO_POOL_SIZE=2` (configured in `my.test.env`) - the minimum that handles concurrent operations without timeouts.
Test environment uses `MONGO_POOL_SIZE=5` (configured in `my.test.env`) - increased from 2 to improve stability during parallel test runs.
- **Prediction Array Truncation:** Prediction arrays (IOB, COB, UAM, ZT) in devicestatus documents are automatically truncated to 288 elements (24 hours of 5-minute readings) before storage. This prevents MongoDB issues with excessively large documents. Controlled by `PREDICTIONS_MAX_SIZE` environment variable:
- **Default:** 288 (truncation enabled)