Data grid
A component for displaying structured data in rows and columns, often with sorting, filtering, editing and selection.
GLOSSARY / SHARED LANGUAGE
A shared vocabulary for the people building, buying and using data-intensive applications.
A component for displaying structured data in rows and columns, often with sorting, filtering, editing and selection.
Rendering only the rows or columns near the visible viewport. It reduces rendering work; it does not necessarily reduce the amount of data held in memory.
Fetching data when needed rather than downloading the entire dataset at once. It is separate from rendering virtualization.
Sorting, filtering or aggregating data in the user's browser. Capacity depends on the data, implementation and device.
Processing data on a backend and returning results to the browser. The grid and API must agree on filters, sorting and pagination.
Logic for table state and operations without a complete, predesigned rendering interface. Your application supplies the UI and its performance characteristics.
Displaying cells with HTML elements. CompareGrids uses the supplied “V-DOM” label for virtualized DOM grids; it should not be confused with a framework's virtual-DOM reconciliation.
Drawing a grid into a canvas surface. Evaluate editing, accessibility and custom cell requirements in the actual implementation.
Organizing rows into sets based on shared values, such as country or department.
Calculating summaries such as sums, averages or counts over a group of records.
Rearranging categories across rows and columns to summarize measures and explore different views of the data.
A conversion of different measurements into points under a chosen scoring system. It depends on the thresholds and included scenarios.
A defined test of specific operations in a specific environment. It is evidence about that setup, not every application.
Creating an Excel workbook. Check whether it includes only loaded rows or all filtered records, and where the export is generated.
The people, applications and deployments permitted by a license. Price alone does not tell you whether a license covers your intended use.
How much work can be completed in a time interval, such as the number of data updates processed each second.
The delay from initiating an operation to receiving its result. Loading, interaction and export can have different sources of delay.
Rows that grow to fit their content. Variable heights can change how a virtualized grid calculates scroll positions.
One cell covering multiple rows or columns, similar to merged cells in a spreadsheet.
Rendering only columns near the horizontal viewport. Particularly relevant for very wide tables.
A grid-specific representation that may reduce transferred bytes or processing work compared with a conventional JSON representation. Compare both size and conversion cost.
Columns that remain visible while other columns scroll horizontally; also called pinned or fixed columns.
A compression format that a server can use when sending assets or data. Plain and compressed sizes answer different questions.
Calculating a score between two known thresholds. This benchmark uses a straight-line calculation between adjacent numeric thresholds.
C: crash; F: fail; B: break; U: unsupported; L: lock or too slow; -: not applicable. See Methodology for how these affect points.
The manually assigned rating of empty space or placeholders during scrolling. The supplied scale runs from 1 (best) to 6 (worst).
The manually assigned rating of how choppy or smooth scrolling feels, from 1 (best) to 6 (worst).
A configured measurement value with an assigned number of points. Thresholds determine the benchmark's scoring priorities.
An integration layer connecting a grid to a framework. Check who maintains it and which framework and grid versions it supports.
A focused prototype using representative data to validate critical requirements before committing to a component.