Long activation time · atom/teletype#201

(2 Kommentare) (1 Reaktion) (0 zugewiesene Personen)JavaScript (2.400 Stars) (416 Forks)batch import

help wanted

Beschreibung

Prerequisites

Put an X between the brackets on this line if you have done all of the following:
- Followed all applicable steps in the debugging guide
- Checked the FAQs on the message board for common solutions
- Checked that your issue isn't already filed?

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

Enable teletype
Reload atom
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

Tech Stack: javascript
Domain: performance
Issue Type: performance
Schwierigkeit: 3
Geschätzte Zeit: half day
Aktivitätsstatus: stale
Klarheit: clear
Voraussetzungen: Atom package developmentJavaScript
Einsteigerfreundlichkeit: 60
Research-Richtung: The issue suggests deferring requires until needed. Look at the main entry point (e.g., index.js or lib/teletype.js) to identify all require statements. Consider lazy loading modules that are only needed for hosting or joining portals. Profile the activation time using Atom's timecop feature to measure improvement. Check if any side effects occur from deferred loading.