onivim/oni

Benchmark typing latency

Open

#90 opened on Dec 12, 2016

View on GitHub
 (6 comments) (3 reactions) (0 assignees)TypeScript (336 forks)batch import
help wantedinsiderperformance

Repository metrics

Stars
 (11,389 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

This article: https://pavelfatin.com/typing-with-pleasure/ has a really great and in-depth investigation into the typing latency of various editors. This latency - the time from pressing the key to seeing the result on the screen - is incredibly important especially with developers. This latency is a huge part in whether an editor is a joy to use or if it feels slow.

For this work, we should look at the following:

  • What are the current measurements of typing latency?
  • What can we do to improve?
  • Can we add metrics so that build-over-build we can see how the latency changes?

Contributor guide

Research direction
Set up a benchmark to measure typing latency using a tool like TypingLatency or custom key press timing. Investigate the current latency by profiling the event loop and rendering pipeline. Consider adding a CI benchmark to track latency over time.
Tech stack
typescript
Domain
performance
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65