if your use-cases can be reduced to exporting an image from an XMP, then darktable-cli is the way to go
if you want to do something more complicated, lua can help a lot. you can specify a lua command on the CLI, you can send lua commands to a running DT via dbus, or you can just write a script... there is even a way to write a lua script that uses DT as a library. It's all documented in the usermanual (btw, the wiki page is not maintained anymore and it has the 1.6 lua API. if you are using the 2.0rc release, you probably want to generate and check the usermanual yourself...) On Thu, Dec 17, 2015 at 11:29 AM, Harald Servat <harald.ser...@bsc.es> wrote: > Hello, > > On 12/17/2015 11:14 AM, Tobias Ellinghaus wrote: > > Am Donnerstag, 17. Dezember 2015, 07:49:23 schrieb Harald Servat > Gelabert: > >> Dear mailing-list, > > > > Hi, > > > >> Is there a way to benchmark darktable? I'm considering on generating > >> some performance numbers using this application but I don't know which > >> should be the best approach to do that. For instance, does it include > >> some sort of headless mode? Can I pass a sequence of commands in a batch > >> file? > >> > >> Any ideas and/or suggestions are welcome. > > > > what exactly do you want to benchmark? The image processing, i.e. the > time it > > takes to export a file? Or the speed of the GUI? Or something else? > > > > The easiest to get numbers from is the image processing part as you can > use > > darktable-cli together with the -d perf option to get numbers for every > > processing step. You would first create an XMP with the desired > processing > > steps, then use that XMP together with an input file to export and > benchmark. > > The command would look something like this: > > > > $ darktable-cli <raw file> <XMP file> foo.pfm --core -d perf > > [dev] took 0.108 secs (0.100 CPU) to load the image. > > [export] creating pixelpipe took 0.128 secs (0.168 CPU) > > [dev_pixelpipe] took 0.000 secs (0.000 CPU) initing base buffer [export] > > [dev_pixelpipe] took 0.018 secs (0.060 CPU) processed `raw black/white > point' > > on CPU, blended on CPU [export] > > [dev_pixelpipe] took 0.006 secs (0.008 CPU) processed `white balance' on > CPU, > > blended on CPU [export] > > [dev_pixelpipe] took 0.004 secs (0.016 CPU) processed `highlight > > reconstruction' on CPU, blended on CPU [export] > > [dev_pixelpipe] took 0.141 secs (0.440 CPU) processed `demosaic' on CPU, > > blended on CPU [export] > > [dev_pixelpipe] took 0.023 secs (0.044 CPU) processed `exposure ' on > CPU, > > blended on CPU [export] > > [dev_pixelpipe] took 0.042 secs (0.160 CPU) processed `base curve ' on > CPU, > > blended on CPU [export] > > [dev_pixelpipe] took 0.049 secs (0.184 CPU) processed `input color > profile' on > > CPU, blended on CPU [export] > > [dev_pixelpipe] took 0.033 secs (0.116 CPU) processed `tone curve ' on > CPU, > > blended on CPU [export] > > [dev_pixelpipe] took 0.108 secs (0.392 CPU) processed `sharpen ' on CPU, > > blended on CPU [export] > > [dev_pixelpipe] took 0.096 secs (0.368 CPU) processed `output color > profile' on > > CPU, blended on CPU [export] > > [dev_process_export] pixel pipeline processing took 0.521 secs (1.792 > CPU) > > [export_job] exported to `foo.pfm' > > Ah! This example is nice. I originally thought that XMP side-files > were useless but here I see their value because I can chain some > transformations! :) I didn't got that from Johannes email, sorry! > > As I mentioned, I'm interested on exploring the performance of > computationally intensive functionalities at the beginning. Depending on > what I see using our tool I'd move to different topics. > > Thank you! > > >> Thank you very much! > > > > Tobias > > > > [...] > > > > > > > > > ------------------------------------------------------------------------------ > > > > > > > > _______________________________________________ > > Darktable-users mailing list > > Darktable-users@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/darktable-users > > > > WARNING / LEGAL TEXT: This message is intended only for the use of the > individual or entity to which it is addressed and may contain > information which is privileged, confidential, proprietary, or exempt > from disclosure under applicable law. If you are not the intended > recipient or the person responsible for delivering the message to the > intended recipient, you are strictly prohibited from disclosing, > distributing, copying, or in any way using this message. If you have > received this communication in error, please notify the sender and > destroy and delete any copies you may have received. > > http://www.bsc.es/disclaimer > > > ------------------------------------------------------------------------------ > _______________________________________________ > Darktable-users mailing list > Darktable-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/darktable-users >
------------------------------------------------------------------------------
_______________________________________________ Darktable-users mailing list Darktable-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-users
