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
The test case might take 2m-5m, maybe there's something wrong with the implementation, or the CI machine gets overloaded during some specific time of the day.
The text was updated successfully, but these errors were encountered:
Looking at the trace on my laptop, we spend a lot of time on I/O for the create relation operations:
That's expected: every time we want to create a relation, we will need to issue an I/O to the disk to check if a key (relation) exists or not. And I don't think there's any easy way to optimize it.
Ideas:
Bloom filter for delta layers so that we don't need to issue I/Os.
If a user is fully migrated to v2, we can skip the check (Postgres shouldn't give us duplicated keys?)
Build a cache for the relation dirs.
Our arm CI machines are bound by I/O. I can observe tests take longer time during our peak hour of development (usually morning eastern US time), which makes tests depending on read/write slower. So I'll leave this issue open and look into ways to further optimize it if necessary.
skyzh
changed the title
pageserver: relv2 test timeout on arm64
pageserver: relv2 test timeout on arm64 / further optimize read latency
Mar 3, 2025
The test case might take 2m-5m, maybe there's something wrong with the implementation, or the CI machine gets overloaded during some specific time of the day.
The text was updated successfully, but these errors were encountered: