Your message dated Wed, 23 Mar 2011 01:08:36 +0100
with message-id <20110323000836.ga1...@jwilk.net>
and subject line Re: Bug#618799: libvigraimpex: unacceptably slow on mips
has caused the Debian Bug report #618799,
regarding libvigraimpex: unacceptably slow on mips
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
618799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libvigraimpex
Version: 1.7.1+dfsg-1
Severity: serious
User: debian-m...@lists.debian.org
Usertags: mips
$ grep -m1 'all 100 trees' *{mips,arm}*log | sort -t _ -k3
libvigraimpex_1.7.1+dfsg-1_armel.log:all 100 trees have been learned in 54688.1
msec
libvigraimpex_1.7.1+dfsg-3_armel.log:all 100 trees have been learned in 56391.8
msec
libvigraimpex_1.7.1+dfsg-2_armel.log:all 100 trees have been learned in 57515.8
msec
libvigraimpex_1.7.1+dfsg-3_mips.log:all 100 trees have been learned in
2.27253e+06 msec
libvigraimpex_1.7.1+dfsg-2_mips.log:all 100 trees have been learned in
2.28524e+06 msec
libvigraimpex_1.7.1+dfsg-1_mipsel.log:all 100 trees have been learned in
13943.6 msec
libvigraimpex_1.7.1+dfsg-3_mipsel.log:all 100 trees have been learned in
16365.9 msec
So it looks like for this particular test mips is ~40 times slower than
armel and ~150 times slower than mipsel.
--
Jakub Wilk
--- End Message ---
--- Begin Message ---
* Aurelien Jarno <aurel...@aurel32.net>, 2011-03-20, 15:04:
- Do you have any ideas what could be the cause of such a bad
efficiency?
gabrielli.d.o and some of the mips buildd don't have FPU, so the
floating point instructions are emulated by the kernel. That explains
why it is so slow. OTOH QEMU is emulating CPU with FPU by default (that
can be changed), so that's why it is faster.
Thanks makes sense, thanks. I'll close the bug then.
BTW, is there a way to programmatically check if FPU is emulated on a
mips machine?
The best is probably to only build this package on a buildd which has
FPU support. I have tweaked the buildd configuration, so it should be
the case now.
Indeed, the package has been successfully built on ball.d.o is less than
3 hours.
--
Jakub Wilk
--- End Message ---
