Because the classification is performed separately from the main thread - it shouldn't affect the performance.
To check the it - I have opened a large enough projects, such as ".NET Framework" sources, and the "Roslyn" sources in Visual Studio with this extension, it works out more quickly than the syntax highlighting built into the IDE.
I use this extension on all my devices and have not yet seen a performance degradation either on a workstation or a low-performance Windows-tablet.
However.
At the moment, there are already several reviews about performance degradation.
Therefore.
If you are observing the same issues yourself - it would be useful for me to learn more about some things:
- In which situations is this observed?
For example: when you open a file, or when you open a project or edit a code, or when switching from one source file to another.
- How exactly does this happen?
For example: the highlighting does not appear for a long time, but the IDE works smoothly, the highlighting does not appear for a long time, and the environment stops in this time or the highlighting does not appear until some correction is made to the code.
- Also, some other details might be useful.
For example: Type of projects on which there is an issue (web, desktop, console, all etc.) or something else that you think is necessary.
- UPD. Performance degradation probably occurs when you edit a files of enormous size. At the moment this is true for abnormally large files (larger than 700 lines).
At the moment, I physically have no time to fix it. As soon as I have a bit more free time - I'll fix this in the next update.
- You could help to speed up this process by making your own fixes on GitHub. And I'll happy to merge it with the "master"-branch and include to release build.