• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.

Nikon z8, RAID, and slowdowns

Status
Not open for further replies.

johnbeardy

Senior Member
Lightroom Guru
Premium Classic Member
Premium Cloud Member
Joined
Oct 8, 2007
Messages
7,324
Location
Leafy Dulwich, S London
Lightroom Experience
Power User
Lightroom Version
Classic
Lightroom Version Number
14.4
Operating System
  1. Windows 11
Has anyone had experience of internal Raid 5 on Windows 11 and delays loading raw files in Develop?

I’ve someone who gets up to a 10 second delay when moving from one Nikon Z8 or Z6II file in Develop. The sliders are unavailable for a few seconds, which I suspect is the raw data loading into the GPU from the hard drive, which is Raid 5. Then everything is normal and there are no signs of anything odd.

I’ll post the gpu details later, but it’s a well above spec nVidia, updated drivers, and the pc has plenty of ram, plenty of disc space.

Update: the GPU is NVIDIA GeForce RTX 3060 (32.0.15.7680) with the preference: GPU for Image Processing Enabled.

It’s a big catalogue, about a million raw files, and the catalogue and images are on this internal Raid drive.

Camera Raw cache has been purged, and set to 20gb.

The delays only seem to occur in Develop moving to the next image. It looks as if they are happening somewhere between storage and gpu, but where and why? Is anything theoretically wrong or risky in this setup?
 
Last edited:
I have never configured raid, so would not give specific advice.

I would check some of thr following:

How many drives should be in the raid setup and if all the drives are online and healthy.

I note the machine is Win 11... was the machine upgraded from Win 10.., are there bios settings askew or driver updates missing for Win 11.

Is the raid compatible with Win 11 .

Are all the disks in the raid the same size... are any running out of space.

Check that there is not a pile of files stored in the rubbish bin .

Has the user upgraded to a bigger megapixel camera. My well performing Win machine started to crawl when I upgraded from a7r3 to a7rv( 40-60MB).

Raid 5 is prone to be slow when writing to disk.. a generic statement... I have no idea what factors influence this (eg file / block size etc) but calculating the strip and parity may take time.

I recognise the raw files are already copied to the disk but I do not know what work files are created when loading a raw file into memory.
 
BTW… Some time back I decided to put a bunch of disks into a Thunderbolt enclosure (I have native Thunderbolt ports in my motherboard)..

On a regular basis I used to get unexplained delays as you describe. Despite using all sorts of diagnostics, measuring I/o speeds, tech support, etc.. I could not eliminate these pauses (which drove me crazy)..

So.. I reverted to putting standard spinning disks inside my pc case for the older years images and kept the last 2 years on an internal Nvme M2 6000MB/ s drive. A year later… I moved my catalog and last 2 years images to an external Samsung T9 connected via Thunderbolt port.

My Thunderbolt enclosure is empty and gathering dust on a shelf…
 
Solution: deleting a LogiOptions plugin from the Modules folder. This was for a Logitech mouse which was damaged a few months ago, and was shown as disabled in Plugin Manager. No idea why this should have slowed down moving between images in Develop.
 
a LogiOptions plugin from the Modules folder. This was for a Logitech mouse which was damaged a few months ago, and was shown as disabled in Plugin Manager. No idea why this should have slowed down moving between images in Develop.
The Logioptions plugin strikes again. There are many posts over the years here and in the Adobe forum about problems caused by that plugin. Logitech utilities silently installed it in the Modules folder. I don't know if the current versions of the utilities still do that.

Even though the plugin was disabled, LR was still executing its Info.LrInitPlugin script (a long-time behavior I've never reported as a bug, because what's the point, in my opinion it will just get designated "as designed" by the LR developers to keep their bug counts low).
 
Yes, remembering old posts about the plugin was what led me to delete it.

I agree that it's clear that the initialisation is not quite right, but it's such a sensitive area. So maybe it's best to let sleeping dogs lie?
 
I replaced all my Logi peripherals ( and their related apps) because I had a sense they were clogging efficient basic o/s features.
 
I've a Logitech trackball but have always preferred not to install their plugins. I'd rather rely on however Windows handles the device - too bad if that means never knowing whatever clever stuff they think I need in Lightroom.
 
I only use external keyboards and mice which have a wired connection… I found I sometimes got lags with wireless. Apple mice might be better … but out of habit bring a small wired mouse for my MacAir when travelling… but rarely use it ( ie 5 click edits max when travelling).

I have keyboard and mouse configured with short cut keys…. which I could not live without and need their apps to configure.

My current and best all time keyboard is Razer BlackWidow Pro.
 
Razer BlackWidow Pro

Whatever one of those may be! I guess I'm not as into gadget (or camera) purchasing as some may be;)

Funnily enough, my first gadget purchase after getting the MacBookPro last year was a Logitech Bluetooth trackball, swiftly followed by USB adapters for its USB-C ports.
 
Good advice I got a long time ago ... which I use...

For stuff you use every day.... "buy the best you can afford".....

and it is a joy to use anything which is fit for purpose.

Well done for tracking down the problem.
 
Good advice I got a long time ago ... which I use...

For stuff you use every day.... "buy the best you can afford".....
Agree completely.
 
Solution: deleting a LogiOptions plugin from the Modules folder. This was for a Logitech mouse which was damaged a few months ago, and was shown as disabled in Plugin Manager. No idea why this should have slowed down moving between images in Develop.
Update again. Thinking that trashing LogiOptions was the solution seems to be a case of wishful thinking :(

The symptoms described here are similar, and the client reports that today's Windows patch has restored normal performance. We'll see....
 
May or may not be relevant.

A few days ago an options screen appeared for a few seconds on my Win pc display... with a title like "Gaming Options"... It was only there for a few seconds so did not get a screen grab or note any details.

I do not have any games installed and have no memory of Gaming options.

I am only in the early stages of exploring this ... but I found a reference where Windows might change the target GPU based on the App / Game and there might delays while this happens.

I am experiencing unstable LrC behaviour... so I am chasing lots of odd stuff... but I am wondering if Microsoft has including a Gaming aspect of Windows in a recent update, which may be tripping up gpu behaviour.

I think anything which operates at a layer just below the user experience may be a factor and I include keyboard oem apps, etc. but dynamic gpu / gaming settings might fit into this category.

I have not had time to follow this yet in more detail, but I intend to give this attention as soon as I can.
 
Someone else looks after the hardware, but I know that the GPU software had been set to a gaming option or configuration. Changing this to a graphics config made no difference.
 
Status
Not open for further replies.
Back
Top