[ImageJ-devel] Labeling - Revised Branch

[Johannes Schindelin]

Hi,

On Tue, 20 Mar 2012, Tobias Pietzsch wrote:

> The main point for you is, that now you can use "smaller" IntegerTypes
> (eg. Byte) to store the Labeling, so you save memory, right?
> 
> That's cool, but it comes with the additional overhead of using a
> SamplerConverter for the Accessors. So you trade of memory vs computation
> time.

If I may enter the discussion: it'd be smashing if that trade-off could be
configured by the caller somehow ;-) Then compute-intensive tasks could
let ImgLib know that they're interested in saving time, not space. And
space-intensive tasks could indicate the opposite.

> Did you do any benchmarks to see how much runtime-overhead you have
> there?

I did a little DuckDuckGo search and it seems as if there is a Performance
Plugin for Jenkins. It can use the output of JUnit, so maybe it would be a
fun thing to implement these performance tests as JUnit tests? Then we
could just configure our Jenkins to test the performance with every new
commit (or at least with as many as Jenkins catches through polling) and
see how performance improves...

Ciao,
Dscho