Reciprocum
Well Known Member
- Followers
- 6
- Following
- 5
- Joined
- Jan 9, 2021
- Posts
- 377
- Likes Received
- 452
- Trophy Points
- 0
- Name
- Afonso Santos
- Country
- Portugal
For file organization purpouses I always create a folder per session and then, under it, subfolders for raw file imports (I name it "%") and JPEG file exports (I name it "$").
During a 6x-recipe 300+ image long export batch I was wondering if there could be any (new) way to improve on the 1h+ rendering times (already have 32GB RAM, eGPU with MacOs has proven to be a rolling disaster full of crashes with each OS upgrade) and then it struck me: I was doing the colossal mistake of having both the RAW files and the export Output location on the same (external Thunderbolt-3 Rocket XTRM-Q SSD) drive !
Just by pointing the export location to my internal SSD drive (eg "Desktop/C1_exports") I cut the export time in half because I can split the input IO (reading the RAWs) from the output IO (writing the JPEGs and TIFFs).
In the end of the export I move the exports to the place I wanted them to be originally. It is one more step in the workflow but it does accelerate it significantly.
During a 6x-recipe 300+ image long export batch I was wondering if there could be any (new) way to improve on the 1h+ rendering times (already have 32GB RAM, eGPU with MacOs has proven to be a rolling disaster full of crashes with each OS upgrade) and then it struck me: I was doing the colossal mistake of having both the RAW files and the export Output location on the same (external Thunderbolt-3 Rocket XTRM-Q SSD) drive !
Just by pointing the export location to my internal SSD drive (eg "Desktop/C1_exports") I cut the export time in half because I can split the input IO (reading the RAWs) from the output IO (writing the JPEGs and TIFFs).
In the end of the export I move the exports to the place I wanted them to be originally. It is one more step in the workflow but it does accelerate it significantly.
Last edited: