Open arjunrajlab opened 2 months ago
If I manually run large_image_converter on this file, it works. The conversion took ~12 minutes on my faster machine. When uploading it, the conversion is VERY slow. I'll look into why.
The file is uncompressed and untiled, which makes for inefficient handling.
Is there a reason it should run slower after upload? It should be running the same command behind the scenes, no?
It probably is because other actions are occurring at the time of upload even before conversion. I think, for instance, that we may kick off some of the caching as soon as the files arrive but before they are composited or transcoded; when we composite or transcode them, some of this action is wasted (but it would have sped things up in instances of single files that aren't transcoded).
Hmm, possibly… although the person who uploaded it in the lab left it running for over 24 hours, and still nothing. I checked the jobs, and Girder didn't seem to be running anything else concurrently (there was some other job that fired up around the same time, but that then seemed to finish relatively quickly). I'll have them try again. Meanwhile, could you send me the command to optimize the file offline using large_image?
The conversion is just large_image_converter <source file> <destination.tiff>
Here's a large TIFF we made that doesn't seem to load properly. We tried both with and without transcoding, no dice.
https://www.dropbox.com/scl/fo/795aptgac63h8l8rkpazj/ACQ-0oEb8rDUunMjK3Q6f14?rlkey=xfi3oj5tb7repcaf6p7k4633w&dl=0