Open audreytoskin opened 7 years ago
@terrycloth Thanks for the issue request. We are currently working on this.
Switching to aspell
from the default hunspell
has taken the activation time on my PC from ~590ms to ~435ms and makes the spell checking of any document that's reasonably sized orders of magnitude faster.
Just want to add that it takes 204ms to activate on my MacBook and Atom 1.19.0, but is the slowest of all my installed packages. The others all take 100ms or less (and I'm working on reducing that too).
Oh, and I'm using Hunspell.
There is a branch where I did some work on attempting to reduce this, the problem is that the code essentially needs a complete rewrite to do things in a way that lets the activation time be down around where it should be.
Atom's "time cop" feature, under Package Loading, shows linter-spell only takes 7 ms, but under Package Activation, it's 12074 ms.
Testing on:
With an AMD Athlon 64 x2 dual core processor 6000+ (a little old).