Image Limits for Sessions UPDATE - Trash ISSUE?
The Problem IS NOT a defective SSD DRIVE.
bought a brand new Samsung T7 1GB. Painfully slow deleting files and clearing trash. On my internal Samsung Evo860 deleting is lightning fast as is deleting trash.
Must be something to do with how files are transfered to and deleted from the trash that External drives don't like. My T7 reads and writes a 500MB/s. Yet it takes 2-3 seconds to delete each image.
I am using a session to store a seasonal sporting event. I import several thousand images, trashing / deleting all buy a couple hundred every week. Deleting an transfers to trash has become so sluggish I can only transfer or delete a couple dozen images at a time or the process takes 30min to hrs to complete. There is currently 4,000 images in the session.
Is there a limit to the number of images a session can handle?
Current Windows 10. C21.
-
Do you empty the session trash from time to time?
Ian
0 -
Yes, I empty the trash most every session update. I have thought about changing to a catalog for this particular customer since there are 40 games a year and I need access to all of them at any given time.
I was hoping a session wouldn't clog up like Adobe does. The storage drive is a Samsung T7 SSD (400+MB/s write avg) with lots of room. The system drive is an NVME m.2 with 32G ram and an RTX 3060Ti graphics card.
0 -
I don't know of any reason why a session should clog up, especially if you empty the session trash.
Ian
0 -
Do you need them in the session trash for a later restore or can you directly delete them from disk?
0 -
Rob,
I have frequently created sessions with several thousand original images shot over several days for a single event and have not observed any significant problems - certainly not of the type you have described. However, I rarely bother to delete so my process is not the same as yours even if the numbers involved can be similar.
One option you might consider is to process each event as a session and perhaps use something like the "Selects" folder concept for the chosen images from the event to group the (currently) chosen images for that event.
For a "master" session covering the whole season (or whatever period is of interest) make another session and add the "Select" folders from the individual shoots as "Favourites" for the new session.
Any further edit work in either the "master" session or the original shoot session applied to the selected images would be available in the master or individual sessions.
Why you should have a problem with deleting in the first place is a puzzle. Ultimately the delete option involves the Windows system trash. Even so I would not imagine that a few thousand files would be a problem unless Windows had problems for some reason.
Maybe the cause lies elsewhere.
Do you have any metadata synchronisation set? Nothing in your description suggests you have but it is one evident function that has potential system overhead and confusion so I thought I would ask the question sooner rather than later.
0 -
Why you should have a problem with deleting in the first place is a puzzle.
My understanding is he deletes them to the session trash. This involves moving all images from Capture to Trash, also all .cos, .comask and thumbnail and preview cache files, and eventually updating the session db.
My observation (some time ago at least, not sure if it was session or catalog) was that when you move images within C1 that it takes much longer than when you do this with Windows Explorer, and my assumption was that maybe C1 copies them first and then deletes them from their source folder, whereas Windows only updates their location in the file allocation table or similar.
0 -
BeO,
Sure, but when I do the same thing (at least in terms of mass deletions although maybe not via via multiple drops into the session trash leading up to it) from time to time the process speed is a non-issue.
That said I have observed Windows (Win 7 - not so obvious ith Win 10 so far) making a bit of a mess of internally managing temporary files and that could cause some issues in some situations.
Rob, as a suggestion you could try re-booting your PC 2 or 3 times consecutuvely WITHOUT starting C1 - or any other application that does not fire up in the Startup process.
I suspect that there is hierarchy of "workfile" cleaning up that occurs at both shutdown and boot and it is possible that the "file cleanup" dependencies do not always allow a complete clean in a single pass.
In some situations there may be some file referencing "Issues" right down in the operating system level that are perpetuated somehow from boot to boot in some specific situations. Rare but not impossible, or so it seems.
Multiple reboots with no related Application activity seems to allow orphaned temporary files to be cleaned up by the OS.
I cannot be certain that my theory of causality is correct but observing seemingly orphaned Temporary files disappear after this sort of action and system performance improve afterwards suggests there may be something in it. With SSDs it should only take a few seconds per reboot to there is little to be lost in trying it.
If the problem persists one might want to some of the MS components for update status - C++ and .NET versions for example.
That would if nothing else, ensure that there should be no OS-level tools problems compounding anything else that might be happening.
0 -
SFA,
Sure, but when I do the same thing (at least in terms of mass deletions although maybe not via via multiple drops into the session trash leading up to it) from time to time the process speed is a non-issue.
Copy & delete wears down SSDs faster than moving files, as each file is written to SSD by the copy process. I don't know though whether or not C1 is actually doing a copy & delete when moving around images in the library tool.
0
Post is closed for comments.
Comments
8 comments