디스크로 스필되는 무제한 결과
정상 동작백프레셔와 디스크 스필로 대용량 결과를 스트리밍합니다. 덕분에 어마어마한 결과 하나가 기기를 먹어치우지 않습니다.
아주 큰 결과 집합이 아주 큰 메모리 문제가 되어서는 안 됩니다. 행은 다음을 통해 스트리밍됩니다 백프레셔 채널 그리고 임계값을 넘어가면, 디스크로 스필, so the grid pages from an on-disk store whether a query returns 50 rows or 50 million.
행이 이동하는 경로
- 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 (함수의 경우 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
그 피벗 그리고 차트 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… 또는 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. 지우기 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.
브라우저에서
그 브라우저 빌드 (the live preview, and SQLly 임베디드 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.
튜닝하기
두 설정은 모두 설정 › 성능 › 쿼리 결과 최적화: 행 임계값과 세트당 메모리 예산(1 MiB~2 GiB)입니다. 메모리가 넉넉하고 더 큰 세트를 정렬하고 싶으면 올리고, 사양이 평범한 머신에서는 낮추세요.