---
title: "Discussion on \"3 Things React Compiler Won't Auto-Memo: From 512ms Down to 6ms\" | Hashnode"
description: "Discussion on \"3 Things React Compiler Won't Auto-Memo: From 512ms Down to 6ms\". I thought React Compiler meant no more manual memo. Then tab-switch took 512ms. Three compiler blind spots — child component boundaries, prop identity intent, and setInterval animation state — with extra everyday examples."
url: "https://hashnode.com/posts/react-compiler-limits/69e7953940ab36d99f973130"
---

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

Discussion

# [3 Things React Compiler Won't Auto-Memo: From 512ms Down to 6ms](https://recca0120.hashnode.dev/react-compiler-limits?utm_source=hashnode&utm_medium=feed)

I thought React Compiler meant no more manual memo. Then tab-switch took 512ms. Three compiler blind spots — child component boundaries, prop identity intent, and setInterval animation state — with extra everyday examples.

Apr 21 · 14 min read · recca0120.hashnode.dev  
Read the article

-   [#performance](https://hashnode.com/tag/performance)
-   [#profiler](https://hashnode.com/tag/profiler)
-   [#react](https://hashnode.com/tag/react)
-   [#react-compiler](https://hashnode.com/tag/react-compiler)
-   [#typescript](https://hashnode.com/tag/typescript)

## Written by

[recca0120](https://hashnode.com/@recca0120)

@recca0120 · Taipei, Taiwan

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

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
