Resultados ilimitados com despejo em disco
funcionalTransmite resultados grandes com contrapressão e despejo em disco, para que uma resposta enorme não devore a máquina.
Um conjunto de resultados muito grande não deve virar um problema de memória do mesmo tamanho. As linhas fluem por um canal com contrapressão e, passado um limite, despejar no disco, so the grid pages from an on-disk store whether a query returns 50 rows or 50 million.
O caminho que uma linha percorre
- The driver batches. Rows come off the wire in batches with a flush timer, so a slow query still shows you what it has rather than nothing.
- The channel pushes back. The queue between driver and UI is bounded. If the grid cannot keep up, the driver waits, which is what stops a fast server from filling memory faster than the app can drain it.
- Past the threshold, it spills. Beyond 50,000 rows (ou um 64 MiB per-set memory budget, whichever comes first) the set is written to a typed binary spill file with its own row-offset index, and the in-memory copy is released.
- The grid pages. A spill-backed set keeps a window of rows resident around your viewport and re-centres it, on a background task, as you scroll. The index is paged too, so the cost does not grow with the size of the set.
You keep working while this happens. The grid paints as rows arrive rather than waiting for completion, the live row count updates as it goes, and repaints are coalesced so streaming a million rows does not spend its time redrawing.
Pivot and chart every row
O Pivô e Gráfico tabs work on spill-backed sets too. Each time you change the layout they read the whole spill file on a background task, showing Pivoting… ou Charting… with a percentage, and memory stays flat however many rows there are. Drill-through works as well: double-click a pivot cell, or click a bar, slice, or histogram bin, and SQLly collects exactly the rows behind it into a temporary file of their own and shows them on the Grid tab under a banner. Limpar brings back every row.
Honest about the trade
Spill files are temporary and owned by the run that made them. Closing the tab or starting a new query deletes them, along with any drill-through files made from them, and a superseded query cleans up after itself even if its results arrive late.
No navegador
O versão para navegador (the live preview, and SQLly Embedded pages) spills too. A browser tab has no disk to write to, so past the same threshold the rows go to the browser's Origin Private File System, private storage the browser keeps for the site. A small background worker owns the files, because only a worker can read and write them synchronously; the app sends it rows in the same spill format the desktop uses and asks it for the rows on screen as you scroll, so the tab's memory stays flat while a multi-million-row result scrolls like a short one.
- What works: scrolling, View Row as Form, copy and export (the first 100,000 rows, like an in-memory export on the desktop), Top Values and profiling, Pivot and Chart over every row, and pivot drill-through.
- Pivot and chart read the stored rows back the first time you open them on a result. The rows are held in the browser's memory, outside the app's own, until the result is replaced.
- Cleanup: the files go when the result is replaced or closed. A tab that closes before it can tidy up leaves them behind, and the next SQLly page in that browser removes them on startup; files another open tab is still using are left alone.
- When it can't: a browser without OPFS, a private window that refuses it, or one with less than about 64 MB of storage free keeps the whole result in memory, as before, and says so in Messages. If storage fills up partway through, SQLly keeps the rows it managed to store and tells you how many.
Ajustando isso
Os dois controles estão em Configurações › Desempenho › Otimizações de resultados de consulta: o limite de linhas e o orçamento de memória por conjunto (1 MiB a 2 GiB). Aumente-os se você tiver memória disponível e quiser ordenar conjuntos maiores; diminua-os em uma máquina modesta.