TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Benchmarking Preact Signals versus the React Alternatives

2 pointsby killcoderabout 2 years ago

1 comment

killcoderabout 2 years ago
With all the recent talk around Preact Signals I decided to clean up and release some benchmarks I did a while ago, and talk about the conceptual differences between the various state management systems available.<p>Originally this post was much longer, but I&#x27;ve split it into two, and I&#x27;ll release the second part once it&#x27;s finished soon (hopefully in a couple of days).<p>This was sparked by Preact Signals monkey patching the renderer in their React package. I thought that such a high maintenance cost decision surely conferred huge performance benefits, when in fact it does not! Though I don&#x27;t show it in this specific benchmark (it&#x27;s in the next post), it&#x27;s more performant to subscribe to the signal and update a regular useState hook in the component, no monkey patching required.<p>I think it&#x27;s helpful to see that these text updates are taking on the order of &lt;20 microseconds on 10 year old hardware, so upending your entire state management solution in pursuit of better performance might not be a sound compromise.