Bug 111088 - Moving a 3D object around in Draw seems to be slower and more CPU consuming compared to 5.1.6.2
Summary: Moving a 3D object around in Draw seems to be slower and more CPU consuming c...
Status: RESOLVED NOTABUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha0+
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-08-02 18:07 UTC by Telesto
Modified: 2017-12-10 20:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Example file (5.52 MB, application/vnd.oasis.opendocument.graphics)
2017-08-02 18:08 UTC, Telesto 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2017-08-02 18:07:57 UTC 
Description:
Moving a 3d object around in Draw seems to be slower and more CPU consuming

Steps to Reproduce:
1. Open the attached file
2. Open the task manager (for monitoring CPU usage)
3. Double click the item (red dots appear)
4. Wobble the image up-down left-right. Compare the speed of 6.0.0.0 with 5.1.6.2

Actual Results:  
LibO6.0 needs consumes more CPU power, rendering it slower

Expected Results:
A bit snappier response


Reproducible: Always

User Profile Reset: No

Additional Info:
Found in:
Version: 6.0.0.0.alpha0+
Build ID: 18f80da7a689ab962735c0f657497b8f1ed4d606
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86@42, Branch:master, Time: 2017-07-28_05:15:48
Locale: nl-NL (nl_NL); Calc: CL

but not in
Versie: 5.1.6.2 
Build ID: 07ac168c60a517dba0f0d7bc7540f5afa45f0909
CPU Threads: 4; Versie besturingssysteem:Windows 6.2; UI Render: standaard; 
Locale: nl-NL (nl_NL); Calc: CL

Note: LibO6 keeps creating/ exiting threads while rotating. 4 threads are launched the first millisecond. The next millisecond 4 Threads are closed. [Monitored with Process Monitor]



User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0
Comment 1 Telesto 2017-08-02 18:08:26 UTC 
Created attachment 135079 [details]
Example file
Comment 2 Buovjaga 2017-08-25 15:24:14 UTC 
I tested with 5.0 vs. 6.0 and 5.0 used about 6% more CPU. 26% peak vs. 20% peak.
What sort of percentages are you seeing?

Win 10
Version: 5.0.2.2 (x64)
Build ID: 37b43f919e4de5eeaca9b9755ed688758a8251fe
Locale: en-US (fi_FI)

Version: 6.0.0.0.alpha0+ (x64)
Build ID: 8d74698f407de0b02826777d5cb3f5aca2fd50f1
CPU threads: 4; OS: Windows 6.19; UI render: default; 
TinderBox: Win-x86_64@42, Branch:master, Time: 2017-08-24_23:26:55
Locale: fi-FI (fi_FI); Calc: group
Comment 3 Telesto 2017-08-25 18:14:42 UTC 
Hmm, not sure why I reported this. The only thing I can think of the endless Threads which are created and destroyed again within a millisecond time-frame (
osl_createSuspendedThread)(process and thread activity in Process Monitor)

Could be nothing at all
Comment 4 tommy27 2017-12-10 17:59:53 UTC 
what should we do about this one? is it still an issue with latest 6.0.x betas?
Comment 5 Telesto 2017-12-10 20:01:58 UTC 
(In reply to tommy27 from comment #4)
> what should we do about this one? is it still an issue with latest 6.0.x
> betas?

Close as not a bug, the measurement is too flaky :-)
Comment 6 Buovjaga 2017-12-10 20:50:52 UTC 
3D object support was removed anyway.