-
-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Case sensitivity seems to have slowed down large scanning by x4 #98
Comments
Thank you. I will speed it up. |
Can you try pinning the version to |
No pressure, just reporting something I hit 😉 |
Please update to |
Thanks, looks like took off 5 minutes from the scan now |
@nschonni It is awesome to see I have done some more work to speed things up. There is still more to do. Especially for the large files. One thing you can do that will take a couple of minutes off of your run time is to create a dictionary for the words. If you copy all the words out of
Update "words": [],
"dictionaryDefinitions": [
{
"name": "custom-words",
"file": "./custom-words.txt", // <-- relative to the `cspell.json` file
"description": "Project Words"
}
],
...
"dictionaries": [
"custom-words", // <-- Any where in the list of dictionaries.
"companies",
"softwareTerms",
"html",
"typescript",
"python",
"node",
"go",
"java",
"csharp"
],
... |
Here are my timing results: Words in
Words in
|
Thanks, I'll take a look at the dictionary idea! I just PR stuff over there to fix it, so I also just have to wait and see if they'll land it 😉 |
@nschonni same here when I use query "some dir/**/*.html" on version 3.2.17 it is 2x times faster than version 4.0.26 ;( |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
EX: on friday the build took around 5 minutes https://dev.azure.com/azure-sdk/public/_build/results?buildId=38575&view=logs
Now it is up to 21 minutes https://dev.azure.com/azure-sdk/public/_build/results?buildId=38845
I'll see if I can trace back to a particular version
The text was updated successfully, but these errors were encountered: