Am Mon, 23 Dec 2019 17:36:04 +0100 schrieb Ulrich Pegelow <[email protected]>:
> Am 23.12.19 um 16:37 schrieb Аl Воgnеr: > > > > 7,393968 [dev_process_export] pixel pipeline processing took 0,608 > > secs (0,915 CPU) > > This is blazingly fast. Did you see the log, there is not a lot of image processing compared to bench.srw. > > Interesting is: > > Spitzlicht-Rekonstruktion' on GPU, blended on GPU [export] > > > > With the bench.srw it was calculated by the cpu. So the use of the > > cpu depends on something and not on the coding of the module itself. > > Probably due to selecting color reconstruction in that module which > has not GPU implementation. > > > > > So my question, if some of these values should be changed, because > > the new system is a lot more powerful: > > > > cache_memory=1073741824 > > maximum_number_tiles=10000 > > metadata/resolution=300 > > opencl_checksum=3732205163 > > opencl_device_priority=*/!0,*/*/* > > opencl_mandatory_timeout=200 > > opencl_memory_requirement=768 > > opencl_micro_nap=1000 > > opencl_number_event_handles=25 > > opencl_size_roundup=16 > > pixelpipe_synchronization_timeout=200 > > plugins/map/max_images_drawn=100 > > plugins/map/max_outline_nodes=10000 > > > > > > Looks good. Make sure to select "very fast GPU" under OpenCL > scheduling profile in preferences->core options. Done, don't know when I can do a comparable test. At the moment a big download is running. No idea, how I got the values above. What does cache_memory influence? No idea, from where this value comes. I could _could_ calcalute this value a long time ago after a recommendation, I don't remember this. How opencl_checksum is calcaluted, this is a value from a rc-file with a total different graphics card. (Geforce GT 1030) Al ____________________________________________________________________________ darktable user mailing list to unsubscribe send a mail to [email protected]
