Bug 107926 - very slow --convert-to on powerful server
Summary: very slow --convert-to on powerful server
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
5.2.6.2 release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: perf
Depends on:
Blocks:
 
Reported: 2017-05-18 08:13 UTC by Dmitriy
Modified: 2018-05-02 15:51 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
diff file between user profiles on CentOS7 and CentOS6.3 (33.58 KB, text/plain)
2017-05-19 10:37 UTC, Dmitriy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dmitriy 2017-05-18 08:13:51 UTC
strange performance situation with command:
    soffice --headless --convert-to *ANY_TYPE* *ANY_FILE*

1) run on Oracle VM VirtualBox machine with 2GB memory, 1 core (intel core i3 2100 on host machine), CentOS 6.3
    convertation took 0.6 - 0.8 seconds
2) run on powerful x86_64 server 32GB memory, 4 6-core CPU AMD Opteron 8431 (24 cores), CentOS 7
    convertation took 6.0 - 8.0 seconds
Comment 1 m_a_riosv 2017-05-18 22:13:12 UTC
Can you test copying the profile from the first to the second, and vice versa to discard something on the configuration making the difference.

https://wiki.documentfoundation.org/UserProfile
Comment 2 Dmitriy 2017-05-19 10:37:31 UTC
Created attachment 133401 [details]
diff file between user profiles on CentOS7 and CentOS6.3
Comment 3 Dmitriy 2017-05-19 10:41:24 UTC
Nothing changed in performance, even when I changed user profiles on each one. The CentOS6.3 VM is still faster than CentOS7 server. Next I'll try to raise new VM with same properties, but with CentOS7.
Comment 4 Dmitriy 2017-05-19 14:12:32 UTC
Remove all rpms from server and install again.
New statistics:
    CentOS7 VM (same properties as another VM, excluding OS)
    real    0m1.408s
    user    0m0.720s
    sys     0m0.100s

    CentOS7 server
    real    0m2.569s
    user    0m2.134s
    sys     0m0.372s

    CentOS6.3 VM
    real    0m0.787s
    user    0m0.673s
    sys     0m0.094s
Comment 5 m_a_riosv 2017-05-19 22:36:54 UTC
I think can be expected the server being a bit slow because their priorities should be on the server side.

Not seems to me an easy task find the reason for the new minor differences.
Comment 6 Dmitriy 2017-05-22 07:19:45 UTC
What do You think if I build libreoffice package on CentOS7, can it fix some problems with performance?
Comment 7 m_a_riosv 2017-05-22 07:55:53 UTC
I can't help on that.
Comment 9 Jean-Baptiste Faure 2017-09-26 04:51:55 UTC
Where are stored the files to be converted in the server case? In other words I guess you have eliminated the network factor?

Set status to NEEDINFO, please set it back to UNCONFIRMED once requested
informations are provided.

Best regards. JBF
Comment 10 QA Administrators 2018-04-04 13:08:37 UTC Comment hidden (obsolete)
Comment 11 QA Administrators 2018-05-02 15:51:25 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20180502