Closed: Catalog sometimes sluggish to repond after query change

[Kirk Baker]

Hayo,

Yeah, truly killing would be potentially bad (memory leaks, still open files, etc.), but it would be great if the thread could be told to not continue processing the now unnecessary image. Could something like that be done?

Given that the earliest the thread could check that its work isn't needed is after the image is 'rendered', there's not much more work that it does (the remaining tasks are not generally time-consuming) before it gets a chance to work on another image.

-Kirk

[Hayo Baan]

Given that the earliest the thread could check that its work isn't needed is after the image is 'rendered', there's not much more work that it does (the remaining tasks are not generally time-consuming) before it gets a chance to work on another image.

Hmm, I guess the rendering is a monolithic process that really cant be interrupted then. That's really a pity since the delay is really painful. Depending on the images (on the discarded contact sheet), the delay could sometimes be > 10 seconds.
Anyway, from what you are describing I don't think we can expect this to be solved soon (if at all). I'm therefore closing the issue.

[Kirk Baker]

Hayo,

Given that the earliest the thread could check that its work isn't needed is after the image is 'rendered', there's not much more work that it does (the remaining tasks are not generally time-consuming) before it gets a chance to work on another image.

Hmm, I guess the rendering is a monolithic process that really cant be interrupted then. That's really a pity since the delay is really painful. Depending on the images (on the discarded contact sheet), the delay could sometimes be > 10 seconds.

Some of the image loaders could be interruptable, some cannot.  It depends on the implementation of the image loader.  Because of it being a not all compliant situation we never put much value in trying to deal with that situation.

-Kirk

[Hayo Baan]

Some of the image loaders could be interruptable, some cannot.  It depends on the implementation of the image loader.  Because of it being a not all compliant situation we never put much value in trying to deal with that situation.

Understandable, especially for the “if it can't work for every loader, we're not putting much effort into this”.