Skip to main content

⚠️ Please note that this topic or post has been archived. The information contained here may no longer be accurate or up-to-date. ⚠️

Sluggish "enumerating" folders that have already been cached

Vincent322
Not sure if it is my setup of Capture Pro 4.7 that is an issue, but the new version (from 3.X) is super sluggish as it traverses the folder hierarchy and presents thumbnails; it is maddeningly slow to where I find the folder I want to work with and never shut capture one down because it is such a time waster. Like it goes thru the 200 directories EACH time and is looking at the contents before it will let you work with it.

Setup:
Alienware dual xeon P3, 4 gb ram running XP
V 4.7 Capture one Pro
Files stored on a Terabyte NAS, not locally

On the older version, it was super snappy once you opened up and it cached the thumbnails, but was slow when "saving" before you shut COP down; this is the reverse, slow to open, but you can shut it down quickly as though changes are saved on the fly.
0

Comments

5 comments

Date Votes
  • Paul Steunebrink
    With CO 3.x preview (a.k.a. cache) files were perhaps stored on the computer's local hard disk, what explains that opening was quick. CO 4.x with NAS put much more strain on the network connection and all the components involved due to storing the cache files with the raw files on the NAS.
    You are correct in your observation that CO 4.x saves settings files on the fly, allowing a quick close of the program.
    0
  • Vincent322
    [quote="Paul_E" wrote:
    CO 4.x with NAS put much more strain on the network connection and all the components involved due to storing the cache files with the raw files on the NAS.
    You are correct in your observation that CO 4.x saves settings files on the fly, allowing a quick close of the program.


    So is it possible to reconfigure to cache previews locally? and still point to the nas? the nas is necessary from a backup standpoint (at this juncture anyway).

    thanks for the response, much appreciated...
    0
  • Paul Steunebrink
    No, you can not configure the cache locally with CO 4.7 or earlier version of CO 4.x (not knowing what the future will bring) while having your raw files on the NAS or network share. Don't know whether you already have a fast (Gigabit) network connection, but that will be your escape.
    0
  • Vincent322
    [quote="Paul_E" wrote:
    No, you can not configure the cache locally with CO 4.7 or earlier version of CO 4.x (not knowing what the future will bring) while having your raw files on the NAS or network share. Don't know whether you already have a fast (Gigabit) network connection, but that will be your escape.


    That's unfortunate. I do have gigabit throughout, so it is likely the disk throughput on the Terastation that is the bottleneck. I think this strategy should be revisited with the design team; assets centralized is not uncommon when you have a LAN with multiple workstations. In this "model" I would have to flip it so my workstation is the primary source, and run sync jobs from the workstation's share so that content is still centralized. Of course that also means my workstation needs massive disk space (in effect doubling my storage requirements.) All that would be unnecessary if caching was local.

    thanks for listening.
    0
  • Lance22
    On installing a trial copy of 4.7 I too found the enumeration of folders is slow as a snail. It takes 90 seconds just to display 320 folder names. This is the case each time I open C1.

    My system is: Vista Ultimate x64 running on Core 2 Quad Q6700 2.67GHz CPU with 8GB DDR2 RAM. RAW files are on their own local drive, and Windows temp/pagefile also have their own drive.

    I'm not sure that C1 is doing anything at this stage apart from enumerating the folders. The "CaptureOne" and "Cache" subfolders are not created until I open the folder. I've tried (and owned) C1 in the past and don't recall seeing this issue before. The operation of C1 is otherwise pretty snappy, e.g. comparable to Adobe LightRoom.
    0

Post is closed for comments.