-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
How to improve spell correction accuracy #58
Comments
Majority of the time is spent creating the dictionary. If your dictionary remain unchanged, you can consider using Some performance comparison : #31 (comment) |
@mammothb Thanks a lot for giving me good suggestion. Now, Above example performance is reduced down from 2.49 sec to 0.9 sec |
Hi @mammothb Is it possible to reduce down spell check correction under 0.2 to 0.3 sec? Regards, |
Hi @mammothb, What parameters should I change to get more spell check correction accuracy? Kindly provide your suggestions. Regards, |
You can try playing around with You can also look at the main project page to check if they have any tips to improve accuracy there. |
@mammothb I am facing an issue in performance, it is taking 1 sec to correct the sentence. How can I reduce down the performance? For this issue any suggestions? Awaiting for your response. Thanks in Advance! Regards, |
Increasing You can also use a smaller I'm not sure if there are other ways if these still cannot get you the speed you want. |
@mammothb Thanks for your suggestions. I have tried below parameters and getting slightly improvement on performance. Can I use multi process on look ups? Regards, |
I have not implemented this port with multiprocessing in mind. You can use multiprocessing with look ups but I was not able to get any improvement in performance. |
Hello Symspellpy team,
How would I improve spell correction performance?
Output Duration: 2.49 sec
To correct a sentence it is taking 2 to 3 seconds which is much higher. Please provide me suggestion or any solutions is available.
Regards,
Hardik
The text was updated successfully, but these errors were encountered: