preactjs / preactjs/preact

App statistics: Help us make Preact even faster

Open
#2,618 28 comments 16 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
38.9k
Forks
2.4k
Avg merge
20h 18m
Merged PRs (30d)
35

Description

🚀 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!

  1. Open Preact Devtools and go to the "Statistics" tab
  2. Click the red "Record" button or the "Reload and record stats" button right next to it
  3. Navigate through your app like a typical user would
  4. 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:

Screenshot from 2020-07-11 16-23-18

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Install Preact Devtools version 1.1.0, open the Statistics tab, record activity in a representative app, and post the resulting screenshot in this issue; that screenshot is the stated completion criterion.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
performance
Issue type
Feature
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.