In redis_keys_view.dart, scanning Redis keys (which works in batches of 100) fetches the type and TTL for each key sequentially:
for (final name in keyNames) {
final type = await widget.connection.keyType(name);
final ttl = await widget.connection.ttl(name);
...
}
This incurs up to 200 sequential network round-trips per batch, creating a severe rendering/loading latency if the connection has even minor network latency.
Steps to fix:
Execute the type and TTL lookups concurrently for the scanned keys using Future.wait or pipeline them.
In redis_keys_view.dart, scanning Redis keys (which works in batches of 100) fetches the type and TTL for each key sequentially:
This incurs up to 200 sequential network round-trips per batch, creating a severe rendering/loading latency if the connection has even minor network latency.
Steps to fix:
Execute the type and TTL lookups concurrently for the scanned keys using
Future.waitor pipeline them.