Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index


I wonder if the poor perf got to do with UNO and Python.  On my Mac, LO ships
with its own Python interpreter instead of just providing the UNO hooks
like it does on Linux.

  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

In every instance, the binaries are provided, I don't build any of them.
What is different, however, is the runtime environment?  Would that make
sense?

Jens

-- 
Jens Tröger
http://savage.light-speed.de/

Context


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.