[Performance] "New Scheduled Trigger" dialog causes severe FPS drops (5-7 FPS) due to background polling in table

[RajuGangitla]

Problem

The "New Scheduled Trigger" dialog causes severe FPS drops (5-7 FPS) when opened, due to background polling firing every 3 seconds and re-rendering the dialog internals.

Please check this Attached Video
https://github.com/user-attachments/assets/23fda2fe-836f-478f-89d2-e1a8e176ad50

Environment

• Page: /{tenantId}/projects/{projectId}/triggers
• Machine: Ubuntu, 32GB RAM, 16 CPU cores
• Polling interval: 3000ms
• Tool used: [React Scan](https://github.com/aidenybai/react-scan) for detecting re-renders and FPS drops

Steps to reproduce

1. Go to Triggers page with at least 1 scheduled trigger
2. Click "+ New Scheduled Trigger" to open the dialog
3. Wait 3 seconds for background poll to fire
4. Observe immediate FPS drop — no further interaction needed

Observed via React Scan

• FPS drops to 5-7 every 3 seconds while dialog is open
• Primitive.div → 344ms per re-render
• Button → 364ms per re-render
• 7x FPS drops recorded
• When dialog is closed, same polling fires with much less impact

Expected

Opening the dialog should have no impact on background polling performance. Re-renders should stay under 16ms to maintain 60 FPS.

[pullfrog]

  ^{｜ Build this ➔ ｜ Make a plan ➔}

[dimaMachina]

I noticed issue with our Tooltip component

agents/agents-manage-ui/src/components/ui/tooltip.tsx

Line 23 in cf6bbb6

<TooltipProvider>

official shadcn's <Tooltip> isn't wrapped with Tooltip.Provider

[RajuGangitla]

yes they removed the tooltip provider at the root
reason: the instantiation of TooltipProvider should be managed by the developer.

please check out this pr once
shadcn-ui/ui#9329

can i raise a pr which will remove the provider at the root and use it at the place where we are using it ?