You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Problem
This test uses a gratuitous number of pageservers (16). This works fine
when there are plenty of system resources, but causes issues on test
runners that have limited resources and run many tests concurrently.
Related: #9802
## Summary of changes
- Split from 2 shards to 4, instead of 4 to 8
- Don't give every shard a separate pageserver, let two locations share
each pageserver.
Net result is 4 pageservers instead of 16
Timeouts on pageserver startup while intializing page cache
https://neon-github-public-dev.s3.amazonaws.com/reports/pr-9637/11892066435/index.html#/testresult/94da16e9e07308f4
Is 16 pageservers too many when multiplied by the page cache size? Is it memory pressure? Should we use fewer pageservers in this test?
The text was updated successfully, but these errors were encountered: