Félix Malfait
2826540bb1
## Summary After migrating from depot.dev runners to GitHub Actions runners, three performance tests are failing due to slower single-threaded performance on the new infrastructure (even with 16 cores). ## Problem The performance tests use React's `<Profiler>` API to measure component render times. depot.dev runners have better single-core performance and lower memory latency compared to GitHub Actions runners, even larger ones. Failed tests: | Test | Threshold | Actual | Overage | |------|-----------|--------|---------| | `DateTimeFieldDisplay` | 0.2ms | 0.281ms | +41% | | `ChipFieldDisplay` | 0.2ms | 0.222ms | +11% | | `RelationToOneFieldDisplay` | 0.22ms | 0.237ms | +8% | ## Solution Increased thresholds to account for GitHub Actions runner performance: - `DateTimeFieldDisplay`: 0.2ms → 0.35ms - `ChipFieldDisplay`: 0.2ms → 0.3ms - `RelationToOneFieldDisplay`: 0.22ms → 0.3ms ## Future Considerations For a more robust long-term solution, we could implement baseline comparison that: 1. Saves performance results on main branch builds 2. Compares PR results against baseline with tolerance (±25%) 3. Self-calibrates to actual runner performance This would catch real regressions without being sensitive to infrastructure differences.
The #1 Open-Source CRM
🌐 Website · 📚 Documentation · 
Roadmap · 
Discord · 
Figma
Installation
See: 🚀 Self-hosting 🖥️ Local Setup
Does the world need another CRM?
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 Recoil, 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!