Erictator wrote: Zenon Char wroteErictator wrotemcbroomf wroteGood to hear Eric, thanks for posting and glad you found the table useful.
The difference may also be influenced by different LR revs which is why I no longer update it. The chart was put together with 12.4. What version of LR were you using? Current (13.2)?Not a fan of LR (I hate that if you want to manually move some files around, it has to re-scan your drive, which can take a whole day with 3TB of pictures... plus I like to do my own filing), but I am using ACR 16.2.1.1767 which had the same issue with AI Denoising speeds, so the chart carries over. I'm on subscription, so yeah, latest PS 25.7 and also have the new BETA loaded of PS 25.9. It was painfully slow before, as you would expect, and I'm getting stuff done in 15sec or less for denoise on my A7RV files, and over-all much faster everywhere in the software. Especially when I open like 100 Raw files at once in ACR, do select-all, and apply the same basic edits to all, it's nearly instantaneous, whereas before I could watch it cycle down the list, heh.
EricFor the benefit of other readers I'm curious about a few things. What you mean about re-scanning files? When you import new files LrC reads the metadata so it can add it to (build) the catalogue, which is just a database. It also builds previews and that can take time. You can choose the Embedded & Sidecar option that lets you cull while the previews build.
My LR folder is on the desktop in Adobe's default - Pictures. That folder contains the Catalogue, Previews and everything else. All my files are stored on an external drive. After a shoot I get the files into a folder that is on my desktop. I import that folder. Once the Previews are built. I leave that folder on my desktop and begin editing. I do this because it is an SSD and the fastest drive. Once done I drag those files to the ED. I've been doing this since 2011 and have never seen LrC reimport, rescan or do anything else. LrC just needs to know where the files are located. Even if my files are on an ED they still open quickly because I keep the previews around forever.
To keep it simple I drag my files from the desktop to the ED using LrC. This way it knows where I moved them and I don't have to remember to tell LrC where I moved then. It still uses the same catalogue and previews that are on the desktop or SSD. That move is as fast as using your OS. I have moved a mass amount of files when replacing a drive and that does take time. For that I use the OS and after I go back into LrC which will show an exclamation mark. I just point it to the root folder at the new location/drive and all is fine. I do this because it is recommended for mass file moves. Again I've never seen any re-scanned or any previews rebuilt. It still uses the original ones wherever your LR folder is located. I've only done that a few times. Any other time I use LrC.
Question about your own filing. You do that either way. LrC does not create its own file system. It uses the existing one, wherever that is located. I can open LrC, the OS, Canon's DPP, DXO, C1 or anything else and it will show the same file structure. My folder structure is by year. In January using LrC I added 2024 and that showed up in the OS file structure.
The only difference between LrC and others is because it's a parametric developer it needs to know where your located and you have complete control over that. You can tell LrC where to import from and where to import to. Again it does not create a duplicate set of files or its own file structure. So the only pain is moving folders/files is using LrC. You can use or OS to do this but then you have to remember to inform LrC about it. I have been moving folders around using LrC for 10 years and never worry about anything. Anything I move something it shows in my OS folder structure or any other developer I open.
You probably don't keep your previews so if you do move 3TB worth of files but that shouldn't affect anything. You are not re-importing, so LrC does not have to build previews. The files metadata is always still in the catalogue database. It only has to build previews for any older folders/files you actually open that do not have the previews stored somewhere.Part of it may be my own fault and initial expectations that got off on the wrong foot years ago... I cut my teeth on Photoshop early days at work. It was expensive back then, and at the time when I first was aware of LR years ago, it was pitched to me as an inexpensive alternative to PS, like "PS Lite" as photo editing software. When I loaded it for home use, it became readily apparent that it was definitely NOT "PS Lite" and that it was primarily an organizer with some editing capabilities.
Fast forward to modern times, I received a free license for LRC with my new Adobe subscription that I bought mainly for PS. So, on a lark, I re-installed LRC to see what's changed.
To be honest, I never bothered to fully flesh it out to see "why" or "what" was happening that triggered a re-scan of my picture drive after I moved some files around via the OS, because I stopped it before it finished, and I yanked it off the system...
...But what I do know, is that after initially installing LR Classic this time around, it took a full day to catalog everything, or whatever it does, and when it did, there was an additional several gigabytes! of index files? and previews? or something? it had created, I dunno, and the work flow just still seemed so foreign to the way I think. It was slow and clunky to me so it was already on probation as far as I was concerned, heh heh. I prefer to rely on the OS logical folder naming conventions and a sort by date function and finding my newest or outstanding unfinished work that way. The tree view and thumbnails just doesn't do it for me.
So, in the end, it sounds like you have way more experience with LR and LRC than I do, and probably can make it sing and dance and it sounds like you really like it. Awesome! Happy for you! It's probably not fair of me to discount it on forums, so I'll watch my rhetoric in the future, but I never wanted an organizer in the first place, so I wasn't inclined to put forth much effort into making it work for me.
NP. It took me while to figure out LrC and the catalogue system. I posted in case others are reading. Nothing wrong someone who does not like a catalogue or LrC's catalogue system. I would hate to see someone not try it out, etc because they think it takes over control. It doesn't. The user has full control. I've opened Canon DPP, DOX, etc edited files and it never affected my LrC edits.
There is not much to it. A few simple rules. Make sure the catalogue knows where all your files are located and when you exit check the Optimization and Check Integrity boxes. When I move or create a new folder/s I use LrC. It isn't any faster using the OS and you can just forget about it.
Yeah the previews can get pretty big. It will build them when you import but not when you move files. So if you import 100,000 files it will take a while. In the catalogue settings you can set up when to discard them. One day, one week, one month or never. I keep them around in case I open old files. Mines about 30GB but I've got the space. My 500GB drive isn't even half full even with the previews.
Lr which has been the cloudy version since 2018 had a big update last fall. I think now it is version 7 and you can store files in the cloud or locally now. It was only cloud storage before that version. It is not as robust as LrC but there is no catalogue either. I can see one day LrC and Lr merging which is fine with me and it seems a natural progression if whatever they call it is as robust as LrC. Then I may try cloud storage. Currently I have no interest and have never installed Lr. If Adobe ever ticks me off the cancel plan button is only 10 seconds away
For others that are reading you can sync LrC to the cloud but it does not send your actual files, only Smart Previews that are so small they do not count towards cloud storage space. You can edit them on other devices including mobile and those edits will sync back to LrC.
Any thanks for replying and good luck in your endeavours.
I just built a new system with a core i9 13900k and an Intel arc a770 16gb and to be honest this card is a steal for what I paid ($200 open box). If someone wants to send me the 60mp test file I can do the denoise timed test in LR to add to the spreadsheet.
I will add that the GPU is very optimized in topaz as that is one of Intel's partners. I was going to buy a refurb 3090 for the 24gb of vram but not really finding a need.
gus6464 wrote:
I just built a new system with a core i9 13900k and an Intel arc a770 16gb and to be honest this card is a steal for what I paid ($200 open box). If someone wants to send me the 60mp test file I can do the denoise timed test in LR to add to the spreadsheet.
I will add that the GPU is very optimized in topaz as that is one of Intel's partners. I was going to buy a refurb 3090 for the 24gb of vram but not really finding a need.
I have not been updating the table as it was made using LRC 12.4 and there were changes to times when Adobe release 13.* It would be good to see what an Intel GPU does though, maybe add it as a footnote. Thanks ...
I have not yet migrated all images from the catalog, but I've copied the LRC catalog onto the 2TB NVMe (OS and programs are on the 1TB NVMe). I copied some images over and ran an Adobe Denoise test (60MP A7R4 test file) and got a time of ~16 seconds (not using a stop watch so might be a sec or so either way). This is a few seconds more than might be from the table, but I'm using LRC 13.2 (current, new install of course), vs 12.4 for the table. Times went up by a few seconds after Adobe switched to compressed DNG when 13 came out so it looks like the machine is on track. A good bit faster than the 3060 in my old PC. Looking forward to seeing how it will do with all other PP once my migration is finished.
How is everyone timing the denoise operation? From beginning to end counting the DNG creation or just the actual process to right before it creates the DNG?
Reason being is that LR says it will take 10s on the (60MP A7R4 test file) with my 3090 gpu but actual is a little less than double because of the DNG creation.
gus6464 wrote:
How is everyone timing the denoise operation? From beginning to end counting the DNG creation or just the actual process to right before it creates the DNG?
Reason being is that LR says it will take 10s on the (60MP A7R4 test file) with my 3090 gpu but actual is a little less than double because of the DNG creation.
We all timed it from when the Enhance Preview window opened and you press Enhance to when the DNG file is created
I have been thinking about upgrading my GPU from a GTX 1660 Ti in my i9-9900 / PCIe 3.0 system to something more powerful to speed up LR Denoise and other AI-based apps (DxO, Topaz).
The discussion here has been very helpful to understand possibilities and limitations of available options. I'm currently looking at RTX 4060 Ti 16 GB vs RTX 4070. Anything more advanced would require a new PSU and is outside my budget.
Since the table on p. 15 does not explicitly mention VRAM but tensor cores -
Can I expect RTX 4070 with more cores but less VRAM to perform better than RTX 4060 with 16 GB ?
capricorn wrote:
I have been thinking about upgrading my GPU from a GTX 1660 Ti in my i9-9900 / PCIe 3.0 system to something more powerful to speed up LR Denoise and other AI-based apps (DxO, Topaz).
The discussion here has been very helpful to understand possibilities and limitations of available options. I'm currently looking at RTX 4060 Ti 16 GB vs RTX 4070. Anything more advanced would require a new PSU and is outside my budget.
Since the table on p. 15 does not explicitly mention VRAM but tensor cores -
Can I expect RTX 4070 with more cores but less VRAM to perform better than RTX 4060 with 16 GB ?...Show more →
Yes, but how much less RAM and how many more cores? That's pretty important. If you are talking about a 4070Ti with 12GB you should be fine.
The numbers in the table are for denoise only of course with the emphasis on Tensor cores. Not sure if Topaz and DXO use them. Topaz seem to be pretty open about answering tech queries so I would ask them.
I think the 4070 was replaced by the 4070 Super at the same price. Might be worth checking that.
mcbroomf wrote:
The numbers in the table are for denoise only of course with the emphasis on Tensor cores. Not sure if Topaz and DXO use them. Topaz seem to be pretty open about answering tech queries so I would ask them.
I think the 4070 was replaced by the 4070 Super at the same price. Might be worth checking that.
The Super is still underpowered compared to the Ti though. Kind of an odd mix of cards:
My constraints:
- budget ~600€
- silent card -> Asus ProArt
- needs to work with existing PSU 600W (max. 650W)
There are just two options left for which the 4070 (OC) seems to be the best, given the fact that for AI Denoise (which is my main use case) the VRAM size doesn't make a difference when looking at the 4060.
My constraints:
- budget ~600€
- silent card -> Asus ProArt
- needs to work with existing PSU 600W (max. 650W)
There are just two options left for which the 4070 (OC) seems to be the best, given the fact that for AI Denoise (which is my main use case) the VRAM size doesn't make a difference when looking at the 4060.
I went with the Asus Dual 4070 OC for similar reasons. I couldn't be happier. The card is quiet, and sips power with silent fan when you are doing normal PC work, and even when processing multiple large 120MB Uncompressed RAW's, it barely spools up at all. I let the ASUS util auto-manage it, and it's never laggy.
I noticed that Art Is Right published a MBA video a couple of months ago. He added a lot of Denoise data and I put together a table and graph showing the effect of the GPU corecount on the time to Denoise. The data was generated using a Nikon 36MP raw file so it can't be compared to the 60MP A7R5 file we have been using. Nevertheless the graph shows the diminishing returns (@ maybe 30 cores) for this one task. He was using LRC 13.2 so this is still GPU cores.
He gave me the OK to republish his data last year. I just sent him a note about the switch to Neural cores with 13.3 and the latest Mac OS so we may see some revised data on one of his next videos
Has there been any testing done on 60 MP files with the RTX 3090 and the RTX 4090? I'm wondering if there is any meaningful increase in performance going from a 3090 to a 4090.
gus6464 wrote:
How is everyone timing the denoise operation? From beginning to end counting the DNG creation or just the actual process to right before it creates the DNG?
Reason being is that LR says it will take 10s on the (60MP A7R4 test file) with my 3090 gpu but actual is a little less than double because of the DNG creation.
What are the specs of your PC? Are you saying that it took almost 20 seconds to denoise and create the new DNG file?
lsquare wrote:
Has there been any testing done on 60 MP files with the RTX 3090 and the RTX 4090? I'm wondering if there is any meaningful increase in performance going from a 3090 to a 4090.
What do you consider meaningful? Everyone's criteria is different.
Bare in mind that you can't compare numbers from the table to tests done today due to the changes in LRC (the table was filled in when we were using 12.3)
mcbroomf wrote: lsquare wroteHas there been any testing done on 60 MP files with the RTX 3090 and the RTX 4090? I'm wondering if there is any meaningful increase in performance going from a 3090 to a 4090.What do you consider meaningful? Everyone's criteria is different.
Bare in mind that you can't compare numbers from the table to tests done today due to the changes in LRC (the table was filled in when we were using 12.3)