First image import / opening takes quite some time

[Rdornier]

I noticed, each time I had to connect again to the OMERO server via ICE api, that the first image import from OMERO is very long. Same for the image opening. When the connection seems to be well established between QuPath and OMERO (i.e. second import or second opening), then it goes way faster.

In order to quantify this time, I did a benchmark of the extension.
It turns out that the time to open the OMERO browser is around 8 times slower and the time to do a first import between 5 to 10 times slower than doing the same with the OMERO-BIOP extension. This is a real bottleneck for us.

The different tests were done using a RJ45 connection, with the qupath-extension-omero-v0.1.0-rc5 and qupath-extension-biop-omero-1.0.3. I listed below everything you may need to redo the tests.

Export to OME-TIFF

The script and the image used are the same as the ones mentionned in that post

Downsample	scaled Downsample	OMERO BIOP Extension	OMERO extension
2	4	83.31s	88.97s
2	4	81.38s	84.11s
1	4	330.84s	345.76s
1	4	359.53s	335.74s

Double-clicking on an image to open it (first opening)

Brightfield H-DAB Dataset
EdU+_RFP+

Image	OMERO BIOP Extension	OMERO extension
Brightfield H-DAB Dataset	5s	25s
Brightfield H-DAB Dataset	5s	25s
EdU+_RFP+	2s	27s
EdU+_RFP+	2s	25s

Opening an OMERO browser

OMERO BIOP Extension	OMERO extension
1s	9s
1.5s	8s

Importing an image from the browser (first import)

Image	OMERO BIOP Extension	OMERO extension
Brightfield H-DAB Dataset	1.5s	18s
Brightfield H-DAB Dataset	2s	18s
EdU+_RFP+	2s	18s
EdU+_RFP+	1.5s	18s

Importing an image from the browser (second import)

Image	OMERO BIOP Extension	OMERO extension
Brightfield H-DAB Dataset	1s	1s
Brightfield H-DAB Dataset	1s	1.5s
EdU+_RFP+	1.5s	2s
EdU+_RFP+	1s	1.5s