atom/teletype

Long activation time

Open

#201 opened on Nov 15, 2017

View on GitHub
 (2 comments) (1 reaction) (0 assignees)JavaScript (416 forks)batch import
help wanted

Repository metrics

Stars
 (2,400 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Prerequisites

  • Put an X between the brackets on this line if you have done all of the following:

Description

Teletype is taking a long time to activate for me at around ~190ms. Looks like deferred activation isn't possible, but would it be feasible to defer some requires until they're needed? For example, until you try to host or join a portal, are the majority of requires needed?

Steps to Reproduce

  1. Enable teletype
  2. Reload atom
  3. Look at how long teletype took to activate

Expected behavior: Preferably <25ms

Actual behavior: ~190ms

Reproduces how often: 100%

Versions

Atom    : 1.24.0-dev-192cde85a
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0

Windows 10 x64.

Contributor guide

Research direction
Analyze the activation path and identify which modules are loaded eagerly. Determine which modules are only needed for hosting or joining portals and defer their loading until those actions are triggered.
Tech stack
javascript
Domain
performance
Issue type
Performance
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.
Half day
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
JavaScriptAtom package development
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60