[Octave-bug-tracker] [bug #61030] [octave forge] (image) Don't use internal function

[Hartmut]

Follow-up Comment #7, bug #61030 (project octave):

For the (only nice to have) test of the excution speed, you could use
something quite simple like this:


clear

tic
for nloop = 1:100
 test bwconncomp
endfor
time_bwconncomp = toc/nloop

tic
for nloop = 1:3
 test imreconstruct
endfor
time_imreconstruct = toc/nloop


Running this (probably only) in the current core Octave release version, one
time with the current image package release, and a second time (on the very
same pc) with the "remove jit" patch applied to the image package (and
properly re-compiled) should be enough to be sure that there are no "dramatic"
speed regressions. We could then conclude something like "the speed decrease
in the relevant BISTs is no more than x% with this patch applied." I know that
BISTs are not made for this, but it would be quite easy to do it like this.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61030>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/