1. According to WebSpellChecker Server Hardware Requirements, 10 MB of cache is enabled on Server for 10000 suggestions. Is it true?
By default, the cache mechanism is turned off. To enable cache saving (caching), specify the number of misspellings using the CacheSaveInterval parameter in the AppServerX.xml file. You can specify any number of misspellings that suits your particular WebSpellChecker needs.
2. Which caching strategy do you use? Are LRU or LFU strategies supported?
We use LRU strategy.
3. Can we control the cache limit? Is it configurable?
Yes, you can control cache limit using the CacheSize parameter in the AppServerX.xml file. It defines a number of misspellings and their suggestions to be cached in RAM.
4. Can we turn off/on the cache?
Yes, you can turn off/on the cache using the CacheSaveInterval or CacheSize parameters in the AppServerX.xml file.
5. Is the cache limit size in MB specified per locale or is it an overall amount?
Cache limit in MB is for overall RAM allocation number.
6. Is caching applicable for both Spelling check and Grammar check functionality? Do you have different cache limit for Spelling and Grammar functionality?
The caching is applicable for spell check functionality only. Yes, if you set the CacheSize parameter value 0, it will turn off the caching, and the suggestions for misspelled words are processed from scratch for every incoming API request.
