June version, no speed improvement

Fri, 26 Jun 2009 00:18:48 Z

Sadly still zero improvement in tile creation speed (load and export times), for large images and large number of images).

What is so disappointing is that the December version had made great progress on that, but all versions since then are abysmal.

How do you go from 4 minutes (December version) to load nine 13k by 13k images, to 6 hours in the last 3 versions.

The tile creation process for large images is ABNORMALLY slow (40mn to load a single 13kx13k image on a core2 duo @ 3Ghz with 3.5Gb of memory!!). and still no multithreading

Regarding large number of images things actually got worse.

Loading time is as bad as the last 2 versions; we went from 3 minutes to load 2000 images of 220x220 in December to 25minutes since then.

Moving to compose with these 2000 loaded images and drop them in the compose area however went from 6mn in December to 12mn in February, to now 15mn. Any manipulation from that point has become more slugish.

But the worse, is that I used to be able to export that composition. In this last version, when clicking the export button, nothing happens, the application hangs there for ever with no processor usage…

One positive to be mentioned, trying to load 2000 images of 890x890 the system used to crash around 500+ images. This version actually loads them all (takes 35mn), but then once in compose (20mn later) arranged them into a grid, doing a frame all crashed DZC.

I guess this app is not being developed to support large compositions which I thought was the goal of a tool like Deep Zoom, or only has very very little resources allocated to its development.

Too bad.

June version, no speed improvement

Sat, 27 Jun 2009 20:32:46 Z

Hi Scrambler,
Deep Zoom Composer is not designed to allow manual compositions that contain more than a few hundred images. That is why we are revamping our current collection exporting functionality where you can import thousands of images and export them by choosing a template. All of this is done without doing the fairly memory and CPU intensive compose step. You can see that in our current preview.

I will see what can be done to alleviate the large image scenarios.

Cheers!
Kirupa

June version, no speed improvement

Sat, 27 Jun 2009 22:27:31 Z

For the large image loading time, may be have a look at what you had done in december :)