Testing times are as follows:
- Code: Select all
version import pyramids total
4.4.6+ [dev_4_4] 25min 55s (N/A) 0s 25min 55s
FS [develop] 28s ~35min ~35min
I've tested importing with our current 4.4.x code. Note that big image ND2 import is known to be slow--the pyramid zoom levels are computed on the client during the import. The intensive computation required to do this slows down the import significantly. The file size is not the limiting factor here, and the filesystem used server side to store the pixel data is unlikely to have a major effect here. The image is viewable immediately following completion of the import.
Just for reference, the current development code using "FS" simply copies the original .nd2 file directly to the server. In this situation, you can see that the import time is vastly smaller, it now being limited primarily by network and disc bandwidth. However, the pyramid zoom levels are now computed server side, so while the import completes quickly on the client, the image is not actually viewable for a while after until this is complete. The speed is limited by the server hardware and the load on the server. In this case, you can see it's a bit slower than before since the CPU in my machine is probably a bit faster than the loaded server.
Regards,
Roger
by jburel » Fri Mar 29, 2013 10:03 am 
