Skip to content

perf: bound peak memory & hot-path algorithms (post-0.4.11 audit) #414

Description

@ZhuchkaTriplesix

Context

Static algorithm review of main (2026-07-27, post-0.4.11 / 0.4.11-a) found remaining peak-memory and hot-path weaknesses. Several older tickets were closed after partial fixes (injectSqlLimit, MySQL rowsStream, CSV isolate, Redis Future.wait) but gaps remain.

Source: Cursor algorithm review of main @ ~9a4648e.

Problem pattern

Cap / display N rows while still materializing the full source in Dart (SQL fetch, export string, zip bytes, RPC JSON line).

Child issues

P0 — peak memory

P1 — UI / I/O latency

Already OK (do not reopen)

Acceptance

  • Child issues linked with Parent: #414
  • Each P0 has measurable memory / streaming acceptance criteria

Metadata

Metadata

Labels

coreCore library logic and servicesepicEpic / umbrella issueperformanceTheme parser epic label: performance

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions