Severe performance degradation on Linux
jens.troeger at light-speed.de
Fri Jan 2 15:37:46 PST 2015
Thank you, Maarten,
I've run office like so from within the Python script:
p = subprocess.Popen("valgrind --tool=callgrind soffice --accept=\"socket,host=localhost,port=2002;urp;StarOffice.ServiceManager\"", shell=True, env=myenv)
and got five callgrind.out.* files once the script terminated soffice.
I ran those through
Note that I'm using the default office image which (I assume) has no
debug symbols. The data doesn't make much sense. Considering the loop
in question ran for about ~45sec (with and without valgrind?!) then I'd
expect an instruction count _much_ larger than a few hundreds of
thousands. In all four profiles, though, libc's _dl_addr and ld's symbol
lookup take most of the time. Not sure I trust these profiles.
On Wed, Dec 31, 2014 at 09:09:19AM +0100, Maarten Hoes wrote:
> Perhaps a wiki page may not be needed after all; it doesnt seem to get
> more complicated than this ? :
> valgrind --tool=callgrind instdir/program/soffice
> And then load the contents of callgrind.out.<pid> in KCachegrind ?
> - Maarten
More information about the LibreOffice