Posts: 34
Threads: 14
Joined: Mar 2015
Posts: 34
Threads: 14
Joined: Mar 2015
Hi Gunther,
When I monitor my CPU usage, for example during initialization and preview generation, it seems as if LRTimelapse only uses one (of my 12) CPU cores. Can you confirm that LRTimelapse was written for only using one CPU core, or do you think other things cause a bottleneck for not using all the CPU-power in my Mac Pro? I am running 32Gb of ram (I allocated 8Gb to LRTimelapse) and the raw image files are on a PCIe SSD which is capable of read/writes of +/- 600MB/s so that would normally not be a bottleneck.
If all of the above is true, have you considered/investigated adapting LRTimelapse to use multiple processors? With the current trend of computers having far more than one CPU core and image files getting bigger and bigger, this would by far be the greatest improvement/feature of LRTimelapse for any (semi-)professional user, since it would save enormous amounts of time, and as you know…. time is money…
Thanks for your insight in this and keep up the good work!
Regards, Jorrit
When I monitor my CPU usage, for example during initialization and preview generation, it seems as if LRTimelapse only uses one (of my 12) CPU cores. Can you confirm that LRTimelapse was written for only using one CPU core, or do you think other things cause a bottleneck for not using all the CPU-power in my Mac Pro? I am running 32Gb of ram (I allocated 8Gb to LRTimelapse) and the raw image files are on a PCIe SSD which is capable of read/writes of +/- 600MB/s so that would normally not be a bottleneck.
If all of the above is true, have you considered/investigated adapting LRTimelapse to use multiple processors? With the current trend of computers having far more than one CPU core and image files getting bigger and bigger, this would by far be the greatest improvement/feature of LRTimelapse for any (semi-)professional user, since it would save enormous amounts of time, and as you know…. time is money…
Thanks for your insight in this and keep up the good work!
Regards, Jorrit