2

Are all C/C++ APIs for example spell(), suggest(); analyse() in the Hunspell library thread-unsafe?

When I use the suggest() API with a lock, I see on an average 50-100 requests for suggestion processed in a second? Did any one try to do benchmarks on this?

Any suggestion for improvement is welcome (including any commercial options for Spell Check and corrections, our web-application is based on C++.)

Mat
  • 202,337
  • 40
  • 393
  • 406
s.s
  • 138
  • 8
  • 2
    I don't know about threads, but to our experience, hunspell is just slow when comes to generating suggestions. The speed we see (when called from Java) is documented at http://wiki.languagetool.org/hunspell-support: 57 sentences/second, 770 sentences/second when not generating suggestions. – Daniel Naber May 05 '13 at 16:14
  • Thanks for the link, i saw in my tests around 50 single word suggestions per second. With increase in number of threads with multiple instances of hunspell my I7 CPU maxed out. – s.s May 06 '13 at 14:25
  • @s.s So you managed to use Hunspell in multiple threads without locking? Because locking effectively makes it kinda single threaded. – Roman Kruglov Dec 13 '17 at 09:24

0 Answers0