Skip to content

perf(redis): pipeline TYPE/TTL for SCAN batches (#187 follow-up) #426

Description

@ZhuchkaTriplesix

Parent

Part of #414

Problem

#187 fixed sequential TYPE/TTL with Future.wait, but each SCAN batch of 100 keys still issues ~200 round-trips (TYPE + TTL per key). Concurrent ≠ pipelined.

Evidence

  • lib/features/redis/redis_keys_view.dart (_scanBatch, ~74–91)

Related

Follow-up to #187.

Acceptance

  • TYPE/TTL for a SCAN batch use Redis pipelining (or equivalent batch API)
  • Measurably fewer RTTs per batch (document before/after)
  • Optional: defer TYPE/TTL until row is visible

Suggested fix

Redis pipeline / MULTI-EXEC batching; or lazy metadata on visibility.

Metadata

Metadata

Labels

connectionsDatabase connections, URI parsing, poolscoreCore library logic and servicesperformanceTheme parser epic label: performance

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions