The following is interesting:
On Sat, Jan 03, 2015 at 05:22:42PM +0100, Jens Tröger wrote:
32b LibreOffice on Mac (py 3.3.5)
Elapsed time: 1.8361830711364746 with 550 pars
64b LibreOffice on Mac (py 3.3.5)
Elapsed time: 0.8173670768737793 with 550 pars
64b LibreOffice on Linux (py 3.4.2) -- Gentoo, Ubuntu, Mint
Elapsed time: 45.529000759124756 with 550 pars
Pipe mode versus socket mode. When I spawn LO to listen to a named pipe
instead of a localhost:2002 socket, then performance is dramatically
different on Linux:
On the remote Gentoo Linux server
Pipe mode: Elapsed time: 0.5140466690063477 with 550 pars
Socket mode: Elapsed time: 45.658066272735596 with 550 pars
On the local Ubuntu Linux machine
Pipe mode: Elapsed time: 0.8761096000671387 with 550 pars
Socket mode: Elapsed time: 45.715266942977905 with 550 pars
On my Mac
Pipe mode: Elapsed time: 1.941413164138794 with 550 pars
Socket mode: Elapsed time: 1.941413164138794 with 550 pars
This doesn't quite solve the problem of why using sockets on Linux is so
much slower, but it does solve the larger problem of having an efficient
connection from an UNO Py client to the office server.
Jens
--
Jens Tröger
http://savage.light-speed.de/
Context
Re: Severe performance degradation on Linux · Jens Tröger
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.