Slow ingest with both PM6 and PM7

[info2x]

Been racking my brain a bit here.

I'm new to using PM to ingest photos.  I've normally used LrC to do that and then PM to do the culling but recently I've had to shoot RAW+JPEG to do some live uploads and sending a JPEG is way way way faster than a raw file and my client can use it directly.  Since LrC doesn't give me the ability to import just the RAW files I figured I'd see how PM6 handled this.  Much to my delight there was such and option.  I started an ingest and I thought I was good to go.  That was the case until I noticed how long it was taking to load files.  I found that when ingesting with PM6 (7269) the speed was being reported as 50 Mb/s.  Using LrC... 500 Mb/s and windows explorer was >600 Mb/s. 

I found this happens on PM6 (7269) and PM7 (7955) on a clean Win10 install.  I just reinstalled windows because I was getting similar performance in LrC but the clean install seems to have fixed that but PM is still being a problem. 

Cards are CF Express and I've tried using two different readers, cables, and thunderbolt vs USB3.  Card doesn't appear stressed in task manager (%active is ~10%) and CPU is also very low (<20%)

[Kirk Baker]

For a problem like this, I suggest contacting our support folks at:

By email: support@camerabits.com

By phone: +1 503.547.2888

Hours: Mon-Fri, 9:00am-5:00pm [PST/PDT]

[info2x]

I can do that.

[Robert Edwards Media]

Hi, I’m not with PM support, but I've faced this issue and thought I’d share something that helped me.  Assuming that you’re running an anti-virus program, see if you can setup an “exclude” exception on the file types you ingest.  For me, this is NEF (Nikon’s raw file format), JPG, XMP and several Capture One file types.

For example, in Bitdefender, I have excluded those file types from “on-access” scans (AV scans that happen when a file is accessed) plus I’ve turned off all AV scans on “Flash Drives” (my card reader & camera's memory cards).  If you’re using another AV package, hopefully it has similar options.

I saw a dramatic improvement in ingest performance thereafter.  And while there *is* some increased risk of infection with some scanning turned off, the risk is worth the reward in my use case.