To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=101629
------- Additional comments from m...@openoffice.org Fri May 8 13:05:33 +0000 2009 ------- Just a general comment to Grammar Checking, maybe also as a reference for future discussions. GC is a very time consuming process and so it is absolutely normal that the Checker fetches a lot of CPU resources. How much that will be and how this influences the time other tasks will get depends on the machine and the implementation. OOo implements Grammar Checking as a real background task, means: a separate thread. If you have a multi core CPU, the Grammar Checker will take a full CPU until the checking finishes. So in case of a dual core CPU and OOo itself (or other apps) just idling while the GC works, you should get ~50% CPU usage. If OOo or another app is also busy, this can give up to 100% of course. But even the single core CPU case not necessarily must impose a problem on the user. Here GC will take up to 100% CPU, but as this work happens in a thread, the operating system will automatically give CPU time to other threads if required. So once you start typing in OOo, OOo will process the input as usual. Due to some synchronisation between the threads the performance will be slightly worse than without the active Grammar Checking thread, but OOo will never block and the performance won't be as bad as "100% CPU for GC" might let you think. I have used Duden Korrektor on a Core 2 Duo Notebook and on a Pentium IV Notebook (single core), both with 2 GHz. On both machines I didn't see any performance problems. The P IV machine was slightly less responsive at times, but it was always bearable. Once the document has been checked completely, the CPU usage wasn't a problem anyway as only modified paragraphs are checked again. --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@sw.openoffice.org For additional commands, e-mail: issues-h...@sw.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
