High package activation time

[borishere]

Hi, sometimes I get high activation time as on screenshot. Is it expected or?

[borishere]

In fact, when I launch Atom, I can work in it only after ~50 seconds (Atom is hanging).
Without 'pigments' package Atom is ready for work after ~7 seconds.

[Cxarli]

Could you please share your Atom version with us? If it is 1.18-beta, #308 could be an issue here.

[borishere]

@C-Bouthoorn I use 1.18.0-beta2.
I discovered that scanning for variables aka color palette causes this hanging. May be the reason is a lot of color variables in my project. Seems that nothing can help me until I disable searching for variables :(

[abe33]

Actually it probably might not be the scanning itself that takes time, as it's an async operation, but rather the deserialization of previously discovered variables. Because scanning a whole project directory takes time and resources the package is using the state serialization mechanism Atom provides to store these variables between sessions, but now it's the serialization/deserialization that become the bottleneck as it's a synchronous operation (I guess they're just JSON.stringify & JSON.parse the whole thing).
I don't really have a plan to rewrite that part to use a different strategy as it'll imply a lot of new issue to tackle. Without knowledge of how is structured it's hard for me to give you a workaround, but generally, if if the project is really huge, with a lot of dependencies, there might be a lot of variables that doesn't come directly from your code but are found in dependencies, and in that case it sometime make sense to excludes these dependencies from pigments' paths to reduce the burden on state serialization.

[Cxarli]

Closing in favour of the master post.