---
title: "Discussion on \"React List Virtualization: Pagination vs Virtual Scroll\" | Hashnode"
description: "Discussion on \"React List Virtualization: Pagination vs Virtual Scroll\". DOM nodes are never free. A table with 3,000 rows rendered all at once means 3,000 nodes consuming memory, participating in style recalculation, and holding layout state — even the rows the user canno"
url: "https://hashnode.com/posts/react-list-virtualization-pagination-vs-virtual-scroll/69f5458fa2d4b01f895ad63f"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [React List Virtualization: Pagination vs Virtual Scroll](https://helloashish.hashnode.dev/react-list-virtualization-pagination-vs-virtual-scroll?utm_source=hashnode&utm_medium=feed)

DOM nodes are never free. A table with 3,000 rows rendered all at once means 3,000 nodes consuming memory, participating in style recalculation, and holding layout state — even the rows the user canno

May 2 · 11 min read · helloashish.hashnode.dev  
Read the article

-   [#performance](https://hashnode.com/tag/performance)
-   [#react](https://hashnode.com/tag/react)
-   [#virtualization](https://hashnode.com/tag/virtualization)
-   [#lists](https://hashnode.com/tag/lists)
-   [#frontend](https://hashnode.com/tag/frontend)

## Written by

[Ashish Kumar](https://hashnode.com/@helloashish)

@helloashish · Delhi, India

  
[View profile](https://hashnode.com/@helloashish)

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

Senior frontend engineer writing about React internals, browser performance, and how big tech builds things. renderlog.in

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
