3 people 03f773f087 redis2: pipeline entry reads when listing a directory (#12042) ...

ListDirectoryEntries fetched every member with its own GET, so a page of
1024 entries cost 1024 round trips. Fetch the values in pipelined batches
of 128 as the loop reaches them and walk the replies in order. Each reply
keeps its own error, so missing and expired members are cleaned up and
skipped exactly as before, and an unreadable member still ends the
listing at that name. Batching keeps a caller that lists with a huge
limit and stops after a few entries from reading the whole directory.

Co-authored-by: Patrick Schmidt <1310072+Woellchen@users.noreply.github.com>
Co-authored-by: user.email <chrislusf@users.noreply.github.com>

2026-10-24 15:04:37 -07:00

..

redis_cluster_store.go

filer: make the redis connection settings configurable (#10441)

2026-07-25 19:55:39 -07:00

redis_sentinel_store.go

filer: make the redis connection settings configurable (#10441)

2026-07-25 19:55:39 -07:00

redis_store.go

filer: make the redis connection settings configurable (#10441)

2026-07-25 19:55:39 -07:00

universal_redis_store_kv.go

redis2: apply keyPrefix in KV methods (#9693)

2026-05-26 12:49:31 -07:00

universal_redis_store_test.go

redis2: pipeline entry reads when listing a directory (#12042)

2026-10-24 15:04:37 -07:00

universal_redis_store.go

redis2: pipeline entry reads when listing a directory (#12042)

2026-10-24 15:04:37 -07:00