App statistics: Help us make Preact even faster
See original GitHub issueš Making Preact even faster
Good news! Weāre experimenting with various ways to speed up Preact even more šÆ To do so we have various enhancements and optimizations planned for our reconciler. So far weāve come up with multiple different approaches that are battling against each other to claim the speed title or be less memory intensive.
Although we do have a small selection of apps to test the various optimizations, we want to make sure that we optimize the things that actually matter most to everyone. We some intuitions what that might be, but itās always better to have some solid data!
For this reason weāve added a new āStatisticsā panel to the Preact Devtools extensions. It allows you to measure statistics for our renderer and will help us get a picture of which optimizations will matter the most.
š How you can help
To start you need to have the Preact Devtools extension installed. Only the latest version (1.1.0
) has the āStatisticsā-tab. The extension is currently waiting approval and you can see the status for your browser below:
- Chrome: Released
- Edge: Released
- Firefox: Released
Now weāre ready to go!
- Open Preact Devtools and go to the āStatisticsā tab
- Click the red āRecordā button or the āReload and record statsā button right next to it
- Navigate through your app like a typical user would
- Post a screenshot of the āStatisticsā-Panel in this thread.
Here is an example of what it looks like after measuring preactjs.com for a while by clicking through various pages:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:14
- Comments:26 (6 by maintainers)
Top GitHub Comments
If itās of use, hereās a small screenshot of the UI that Iām building. Itās a toy Bayesian network modeller. Everything is a Preact component. Data is adjusted using sliders which are drag-to-resize divs, which causes lots of re-rendering. Iāll probably refactor that at some point. Probably š