On 2015-02-11 05:07, Andriy Rysin wrote: > 1) it seems like we're currently creating and destorying thread pool > every time we check sentences, would it not make more sense to create > pool once and keep threads in the pool and reuse them?
I think so. The number of threads should then probably be specified via constructor, not via a set method, so it cannot be changed. > So I am wondering if somebody can shed a bit more light on what are > the critical parts that are not thread-safe and is it worth exploring > if they can be paralellized or it's too much work for not much gain? I don't think there's a better way than carefully looking at the code to make sure it's thread-safe *and* have extensive tests that run with several threads (not as active unit tests, as they run too long). But I think it makes sense to make more code run in parallel. Regards Daniel ------------------------------------------------------------------------------ Dive into the World of Parallel Programming. The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Languagetool-devel mailing list Languagetool-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/languagetool-devel
