## RecordTable Performance Investigation & Optimization (WIP) Investigates what makes the RecordTable slow (14 components, ~12 hooks per cell) and starts applying fixes. ### Key Findings (2,000 cells benchmark)   - **Jotai atoms are the dominant cost**: 10 atom reads/cell = +312%. Full sim with atoms = +476%. - **Derived atoms are 3x cheaper** than individual reads (12 sources: +93% vs +294%). - **Component depth is expensive**: 4-level nesting = +82%, 14 wrappers = +109%. - **Styling engines are comparable**: Linaria vs Emotion is within noise. - **Context reads and useState are nearly free** vs baseline. ### Optimizations Applied 1. **Static focus providers** — replaced per-cell `useState(false)` with static context. Eliminates 400 useState instances. 2. **Delegated onMouseMove** — single handler on table body instead of 400 per-cell handlers. 3. **Hoisted `useObjectMetadataItems()`** — moved from per-cell to table-level context. Eliminates 400 global atom reads. ### Tooling - Perf page at `/__perf__/table`: 17 cell render + 13 state access benchmarks - Render profiler: `window.__RECORD_TABLE_PROFILE = true` - Full plan in `__perf__/PERFORMANCE_PLAN.md` ### Remaining Phases (not high priority to-be-honest) | Phase | What | Status | |-------|------|--------| | 1 | Separate display from interaction | Partial | | 2 | Flatten hierarchy (14 → ~5 components/cell) | TODO | | 3 | Reduce atom reads per cell | Partial | | 4 | CSS-only hover/focus | TODO | | 5 | Event delegation, lazy Draggable | TODO |
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · Roadmap ·
Discord ·
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Why Twenty
We built Twenty for three reasons:
CRMs are too expensive, and users are trapped. Companies use locked-in customer data to hike prices. It shouldn't be that way.
A fresh start is required to build a better experience. We can learn from past mistakes and craft a cohesive experience inspired by new UX patterns from tools like Notion, Airtable or Linear.
We believe in Open-source and community. Hundreds of developers are already building Twenty together. Once we have plugin capabilities, a whole ecosystem will grow around it.
What You Can Do With Twenty
Please feel free to flag any specific needs you have by creating an issue.
Below are a few features we have implemented to date:
- Personalize layouts with filters, sort, group by, kanban and table views
- Customize your objects and fields
- Create and manage permissions with custom roles
- Automate workflow with triggers and actions
- Emails, calendar events, files, and more
Personalize layouts with filters, sort, group by, kanban and table views
Customize your objects and fields
Create and manage permissions with custom roles
Automate workflow with triggers and actions
Emails, calendar events, files, and more
Stack
- TypeScript
- Nx
- NestJS, with BullMQ, PostgreSQL, Redis
- React, with Jotai, Emotion and Lingui
Thanks
Thanks to these amazing services that we use and recommend for UI testing (Chromatic), code review (Greptile), catching bugs (Sentry) and translating (Crowdin).
Join the Community
- Star the repo
- Subscribe to releases (watch -> custom -> releases)
- Follow us on Twitter or LinkedIn
- Join our Discord
- Improve translations on Crowdin
- Contributions are, of course, most welcome!




