Suggest an editImprove this articleRefine the answer for “Why are signals considered more performant than RxJS?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Signals** are faster because they work in a targeted, synchronous way, without unnecessary subscriptions and without passing data through a stream. **Key point:** Signals are "direct reactivity without intermediaries", they do less unnecessary work, so they run faster.Shown above the full answer for quick recall.Answer (EN)ImageSignals are faster because they work in a **targeted, synchronous** way, without unnecessary subscriptions and without passing data through a stream. ### Main reasons: 1. **No subscriptions.** A signal is simply a value in memory. On change, Angular knows who to update, without the `subscribe()` and `unsubscribe()` mechanism. 2. **Synchronous work.** When you call `set()`, the update happens immediately. RxJS often processes events asynchronously, through a task queue. 3. **Precise template updates.** Angular with signals updates only the elements where the signal is actually used, not the whole component. 4. **Less overhead.** RxJS has a complex mechanism of streams, operators, and subscriptions. Signals have a simple model of storage and reaction. **Summary:** Signals are "direct reactivity without intermediaries". They do less unnecessary work, so they run faster.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.