Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Performance: Slow Screen Redrawing in All Apps | ||
---|---|---|---|
Product: | ui | Reporter: | jwernerny <flybrick> |
Component: | ui | Assignee: | jwernerny <flybrick> |
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@ui <issues> |
Severity: | Trivial | ||
Priority: | P3 | CC: | harlan, issues, marius.andreiana, mmeeks, thorsten.martens, thorsten.ziehm, utomo.prawiro |
Version: | 643 | Keywords: | oooqa, performance, regression |
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
jwernerny
2002-10-22 16:16:15 UTC
Does 1.1beta2 have the same speed problem for you? How much RAM do you have, and what processor / speed is your computer? 1.1Beta and 1.1Beta2 seem to have sped things up a bit more. [I think it may still be slower than 1.0.x, but I haven't checked those recently.] The original report was on a 400 Mhz GenuineIntel Pentium(r) II Processor Intel MMX(TM) Technology with 224MB RAM. I also experienced similar performance hits on other, slower machines. If there is any way to keep speeding the display up, I think it would be good. I expect a great number of people who are looking seriously at Open/StarOffice are not the ones who are running 2+ Ghz machines. They are more likely to have a "bargain" priced machine and are looking for the lowest cost solution they can get. OK, but are you willing to say it's fast enough now to not be defective? :-) I bet you are, so I'm going to change the class of this bug from 'defect' to 'enhancement' :-) Reassigned to Bettina. . This should be a defect. With snapshot 1.9.54 on Fedora core, sometimes just moving the cursor with arrow keys it's visibly slow, even on a new 1 page document. top shows soffice.bin using 70% of cpu after moving cursor (760 mb ram, 1.7ghz celeron). There are no other processes using significant CPU. Unfortunatelly it doesn't happen 100% of the time and I don't know how to reproduce. can you please try OOo 2.2 please as that version is much faster. Thanks *** Issue 78780 has been marked as a duplicate of this issue. *** os all. is this UI or framework ? I think it maybe framework I suspect framework, and that the UI slowdown is just a symptom, but it could well be instability in the UI. To clarify, this is NOT a performance bug, this is a stability bug! Issue type should NOT be "enhancement", but should be "defect". This has nothing to do with the speed of the machine, and it causes dataloss. I would ask that the bug be reclassified appropriately. Please see Issue 78780 for my more detailed report. (If in fact this bug and that bug are different issues, then 78780 should of course be reopened.) Just a ping on this issue to again requent the change of the issue type from "enhancement" to "defect". I do not have the permission to do so myself. If this issue is seen as a separate issue from 78780, then I will reopen that bug. I'll echo harlan879, and his bug report in Issue 78780 - if that is a separate issue it needs to reopened, as this problem in OO2.2 is very frustrating. Sometimes it works for a few hours, sometimes a few minutes, before this occurs. As I'm currently working on several large documents at once, this can chew up 10-15 minutes to try to save & shutdown once this occurs. After closing everything and restarting OO, everything is once again fine. I've not actually experienced crashes. I've seen it occur even if I only have a large Writer document open, but it is far more likely to be triggered by a spreadsheet. I'm runing Ubuntu 7.04, Gnome. I see this on two systems with no hardware in common, and on neither have I had anything like this occuring prior to 2.2. This is regression and performance problems. and many people complains about OOo performance. I hope we can reduce it. Thanks reassign to ka. Could you use OOo 3.1.1 or even 3.2 Beta and tell me if this is still an issue for you, please?. Especially for OOo 3.1, there were quite a lot of performance improvements made to the whole office code in all applications. If you can still reproduce this issue with a recent release (see above), please tell me exactly when/how/... this happens and how we may reproduce it inhouse. The original issue was reported 7 yaers ago against a pre-release version. Since then, the issue has morphed ino something else that is followung new versions. Since logging the issue I have upgraded PCs and OSes to the point that this is no longer a problem for me. BUT, there is still an issue for some. Personally, I would be happy to close this, but others may not be. For now, I'm going to bounce this to "works for me", but encourage those who still consider it a problem to chime in. - John worksforme -> duplicate |