2.3b2: Slow commands (several seconds) under SunOS / Sparc
Jari Aalto
jari.aalto at cante.net
Thu Nov 18 11:37:18 GMT 2010
2010-11-18 09:34 "Voelker, Bernhard"
<bernhard.voelker at siemens-enterprise.com>:
> Jari Aalto wrote:
>
>> System Configuration: Sun Microsystems sun4u Sun Serverblade1 (UltraSPARC-IIe 650MHz)
>
> I guess it's ~6years old (it's SunOS5.9) and therefore should be still quite ok. ;-)
>
>> I'm attaching "truss -f" of "bzr help" below for more information about
>> syscalls.
>
> From the failing open64() calls in your truss output, these look quite strange:
>
> 8759: open64("/mnt/cc/staff-f/jaalto/tmp/vc/xx/test/sre_compile.so", O_RDONLY) Err#2 ENOENT
>
> This could be a directory on a slow (or even down?) remote file system.
> However, I guess ld() should not search there (and maybe in other directories).
> Are you sure your LD_LIBRARY_PATH is okay? It seems that there are a few entries
> which should not be there - at least for running bzr.
I'm wonderign why doe sit even display susch paths. I just tested with:
cd ~/tmp
env \
PATH="/usr/local/bin/gnu:/usr/local/bin:/usr/bin:/opt/csw/bin:$PATH" \
LD_LIBRARY_PATH="/usr/local/lib:/opt/csw/lib:/usr/lib:/usr/lib/secure" \
PYTHONPATH="/usr/local/lib/python:$PYTHONPATH" \
truss -f bzr help |
grep staff-f
And it displays loads of calls under the PWD (~/tmp)
# note: I have hundreads of files and dirs under ~/tmp
...
/mnt/cc/staff-f/jaalto/tmp/timemodule.so",
"/mnt/cc/staff-f/jaalto/tmp/traceback",
"/mnt/cc/staff-f/jaalto/tmp/traceback.py",
"/mnt/cc/staff-f/jaalto/tmp/traceback.pyc",
"/mnt/cc/staff-f/jaalto/tmp/traceback.so",
"/mnt/cc/staff-f/jaalto/tmp/tracebackmodule.so",
"/mnt/cc/staff-f/jaalto/tmp/tty",
"/mnt/cc/staff-f/jaalto/tmp/tty.py",
"/mnt/cc/staff-f/jaalto/tmp/tty.pyc",
"/mnt/cc/staff-f/jaalto/tmp/tty.so",
"/mnt/cc/staff-f/jaalto/tmp/ttymodule.so",
"/mnt/cc/staff-f/jaalto/tmp/urllib",
"/mnt/cc/staff-f/jaalto/tmp/urllib.py",
"/mnt/cc/staff-f/jaalto/tmp/urllib.pyc",
"/mnt/cc/staff-f/jaalto/tmp/urllib.so",
...
Does bzr or python somehow search "." or do I have a problem in my setup
somewhere?
Neither PATH or PYTHONPATH used above contain "." or "::" (empty path).
Jari
More information about the bazaar
mailing list