Check catalog performance during imagedrawer image upload operation

[Balazs Ree]

When an image is uploaded with the imagedrawer, in order to maximize performance we want to make sure that the newly created image is cataloged once only: ie, there are no subsequent recatalog operations within the same request.

If we want to be sure about this we need a way to check this. Best would be to have a unittest that checks this, but a one time check would be fine too.

If there are more recatalog operations for some inherent reason, I believe we can live with that but we should be aware.

[Paul Everitt (paul-agendaless)]

We'll see if Chris can look at this in the next milestone after this one.

[Paul Everitt (paul-agendaless)]

Handing some things over to Tres.

[Tres Seaver (tseaver)]

Any extraneous indexing would be happening as the images are added / removed
from the tempfolder: I can see no valid case for having content which is in that
folder be indexed at all.

Suppressing the unwanted index / unindex should be as simple as overriding
the 'add' and 'remove' methods on karl.models.tempfolder.TempFolder, making the
'send_events' default to False. Plus testing for the non-publication of the events,
of course.

[Tres Seaver (tseaver)]

Fix committed, with tests, on a branch:

 svn+ssh://<email address hidden>/home/osi/bfgsvn/karl/branches/lp592697

[Paul Everitt (paul-agendaless)]

Got done in M43.

[Tres Seaver (tseaver)]

I just merged the branch to the trunk.

[Paul Everitt (paul-agendaless)]

Not really testable, I'll go ahead and mark as done.