On Wed, Jul 28, 2010 at 23:01, Edouard Gomez <[email protected]> wrote:
> I was trying to dedicate some time to profile rawstudio using the perf
> profiler available with recent linux kernels.
>
> And I'm quite pleased with its ease of use compared to oprofile :-)
>
> However, for profiling/benchmark reproductabilty purposes, i was hoping i
> could easily build a RS_QUEUE and start a batch processing.
>
> I've read rs-batch.c and... hmmm, a too big challenge just for benchmark
> purposes :-) GUI code is so deeply nested in the processing code that i
> don't see how i can process an image w/o starting the GUI.
>
RS_QUEUE *queue;
queue = rs_batch_new_queue();
rs_batch_add_to_queue(queue, "/path/to/filename.raw", 0);
rs_batch_add_to_queue(queue, "/path/to/filename2.raw", 0);
rs_batch_process(queue);
g_object_unref(queue);
.. should do the trick.
You will probably see that saving the output file is almost the slowest part
of the process. In the future the compression step could be made
asynchronious - that is "merely" a question of modifying the output filters.
> The plan was to simply replace the test function so that it loads files and
> process them one by one, using a specific settings file.
>
> Out of curiosity, I tried to find if there was a simple
> filename>photo>processing function and I've been a bit surprised the
> rs-batch code would do the processing quite differently from "export as" or
> "quick export".
>
Yes - I completely agree - this has been a reason for a number of problems,
and I think that in the future some of the functionality could be merged
into a separate function.
> Is it planned for the core processing of a photo to be decoupled from the
> GUI direct calls ?
> GUI updates can be handled through carefully designed hooks/callbacks.
>
Quick Export is an obvois canidate for separation, since it would be much
nicer, if it ran in a separate thread. We have however not pursued this
heavily, since the lack of thread priorities in Linux will make the UI very
un-responsive, if we for example ran Batch Export in a separate thread. It
has been on my wish-list, but since batch export is so CPU demanding I think
it will kill the main UI experience anyway.
>
> --
> Edouard Gomez
>
Regards, Klaus Post
http://www.klauspost.com
_______________________________________________
Rawstudio-dev mailing list
[email protected]
http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
