Extreme CPU use when (I think) resolving very large localisation files about paradox-language-support HOT 6 CLOSED

The PLS plugin developed by me has been made several optimization for memory and cpu usage. Please try the lastest plugin version (1.0.8, will be visible on plugin marketplace soon) and recheck the performace.
Until now, the cpu and memory usage during indexing is still not ideal (but it need to be for it's indexing logic), the cpu and momoery usage of code completion and reference resolving should be pretty good for script and localisation files up to thousands of lines.

from paradox-language-support.

Besides, you can try:

• suppress inspections for very large files. (usually, add "# noinspection ALL" at the first line)
• disable related inlay hints (e.g. inlay hints of localisation icon)

from paradox-language-support.

If what you mention is localisation references ($LOC$), since 1.0.7, the performance to resolve these should be optimized.

from paradox-language-support.

It seems I was on 0.10.2 before. I just updated to 1.0.7 and will check out performance now.

from paradox-language-support.

Oh wow, that's an incredible improvement! It only took around 3 seconds even on our main file, which is nearly 20000 lines long.

I think everything is working now, thank you.

I encountered the issues a week or two ago, but I should have checked for a newer version before posting an issue. Apologies for the inconvenience.

from paradox-language-support.

The main performance issue is not for localisations, but for ... you can try to find out them XD.

from paradox-language-support.