I have 2 questions about MultiThreadedJLanguageTool: 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? It probably would not improve performance much but it seems to be more correct 2) it looks like we currently only use threads for checking sentences which uses ~30% of my 4 cpus on i3; I tried a quick change to run sentence analyzer in threads and it bumped cpu usage to ~50%; I did the sentence analyzing separate from checking so it's not the most efficient way (it could be done better) but it shows there's room for improvement. Also I intentionally didn't care about correctness in this test - there are some comments about JLanguageTool not being thread-safe. 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?
Thanks Andriy ------------------------------------------------------------------------------ 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
