memory and performance - has something changed?
I recently had to completely reinstall Windows 10 and start fresh, including reinstalling C1. This brought me 10.2, and I just recently started doing some photo work again after a long break.
With a fresh Win10 installation I'd have expected things to run pretty well but C1 seems MUCH slower than I remember it from a few months ago. Startup (loading a catalog) takes ages, and after editing for a while, C1 completely strangles my system. Yesterday, it totally hung while exporting a JPG, I had to exit C1 despite the warning of export in progress.
I don't want to just whine, I know it's complicated and I want to address the problem. I have a 3 GHz 4 core CPU from 4 years ago, 8gb RAM and probably a low end GPU. Is 8GB really enough for C1 today, with 24mb raw files? Has something changed with memory management at 10.2? Are there some cacheing, or thumbnail options I've forgotten about, that greatly affect performance? Are there any C1 performance tips on this web site or elsewhere?
I'm committed to C1 but I've got to get some improvement in performance. I just don't know what to throw that money at.
With a fresh Win10 installation I'd have expected things to run pretty well but C1 seems MUCH slower than I remember it from a few months ago. Startup (loading a catalog) takes ages, and after editing for a while, C1 completely strangles my system. Yesterday, it totally hung while exporting a JPG, I had to exit C1 despite the warning of export in progress.
I don't want to just whine, I know it's complicated and I want to address the problem. I have a 3 GHz 4 core CPU from 4 years ago, 8gb RAM and probably a low end GPU. Is 8GB really enough for C1 today, with 24mb raw files? Has something changed with memory management at 10.2? Are there some cacheing, or thumbnail options I've forgotten about, that greatly affect performance? Are there any C1 performance tips on this web site or elsewhere?
I'm committed to C1 but I've got to get some improvement in performance. I just don't know what to throw that money at.
0
-
[quote="NN635790973675498599UL" wrote:
I recently had to completely reinstall Windows 10 and start fresh, including reinstalling C1. This brought me 10.2, and I just recently started doing some photo work again after a long break.
I feel like something has changed. With a fresh Win10 installation I'd have expected things to run pretty well but C1 seems much slower than I remember it from a few months ago. Startup (loading a catalog) takes ages, and after editing for a while, C1 completely strangles my system, which has 8GB. Yesterday, it basically hung while exporting a JPG, I had to exit C1 despite a warning of an export in progress.
I don't want to just complain about performance, I know how complicated it is and I want to address the problem.
I have a 3 GHz 4 core CPU from 4 years ago, and probably a low end GPU. Is 8GB really enough for C1 today, with 24mb raw files? Has something changed with memory management at 10.2? Are there some cacheing, or thumbnail options I've forgotten about, that greatly affect performance>
Are there any C1 performance tips on this web site or elsewhere?
I'm committed to C1 but I've got to get some improvement in performance even if that means spending money. I just don't know what to throw that money at.
Similar here. 8GB of RAM.
10.1 introduced several issues in preview generation, and I think 10.2 still has those issues under a band-aid; with perhaps a memory hole somewhere on top.
If I open 10.2 in a folder with previews to be generated, CO will start hogging ram until there's none available. 4GB + for the CO process and another half gig or so for the renderer. That means that if I have Chrome and my hoardy share of tabs open, the system becomes unusable.
(Edit: To do the same job 10.0.2 rarely passes 2GB)
I'm in the process of reporting some behavioural issues, but haven't quite hit the right state of mind to get thorough on the support case.
I think I will ask for a switch that lets you stop automatic preview generation to be added either way.
10.0.2 has no hardware acceleration for Fujifilm files, and it's share of bugs, but performace is fairly consistent.0 -
[quote="gusferlizi" wrote:
If I open 10.2 in a folder with previews to be generated, CO will start hogging ram until there's none available. 4GB + for the CO process and another half gig or so for the renderer. That means that if I have Chrome and my hoardy share of tabs open, the system becomes unusable.
Yes that's just what I see Task Manager. Depressing. I wonder if C1's main process can even use more than 4GB as it seems to stop there.0 -
10.2 has my system in a grip of death. I need to do something.
It's very slow to start, very slow to shut down, and quickly sucks up all the memory it can get in my system. I can't do a thing while it's running - email, browser, all completely stalled and I see 96% memory usage.
PhaseOne does, of course, have 'hardware requirements' posted, including a recommendation of 16gb for editing 'high-resolution images". But are these recommendations up to date?
How much memory, how many cores, do I need to supply C1 to really make a difference?0 -
[quote="NN635790973675498599UL" wrote:
10.2 has my system in a grip of death. I need to do something.
It's very slow to start, very slow to shut down, and quickly sucks up all the memory it can get in my system. I can't do a thing while it's running - email, browser, all completely stalled and I see 96% memory usage.
PhaseOne does, of course, have 'hardware requirements' posted, including a recommendation of 16gb for editing 'high-resolution images". But are these recommendations up to date?
How much memory, how many cores, do I need to supply C1 to really make a difference?
If I were you I would create a Support Case and get some input from the C1 support team.
What you describe does not sound at all normal and I would suspect that there might be something awry with some aspects of the installation compared to your system configuration.
What did you have before 10.2?
Are you running any meta data synchronising betweens applications?
I assume you have already tried a system reboot?
Grant0 -
[quote="SFA" wrote:
If I were you I would create a Support Case and get some input from the C1 support team.
What you describe does not sound at all normal and I would suspect that there might be something awry with some aspects of the installation compared to your system configuration.
What did you have before 10.2?
Are you running any meta data synchronising betweens applications?
I assume you have already tried a system reboot?
Grant
See my OP - this is a recent Win10 installation. No metadata syncrhonization (what's that?).
C1 doesn't take all the memory right away. But after I've edited a number of photos, C1 has 5GB and never gives any of it back.0 -
[quote="NN635790973675498599UL" wrote:
No metadata syncrhonization (what's that?).
Show in settings. There is a point about metadata sync0 -
[quote="NN635790973675498599UL" wrote:
[quote="SFA" wrote:
If I were you I would create a Support Case and get some input from the C1 support team.
What you describe does not sound at all normal and I would suspect that there might be something awry with some aspects of the installation compared to your system configuration.
What did you have before 10.2?
Are you running any meta data synchronising betweens applications?
I assume you have already tried a system reboot?
Grant
See my OP - this is a recent Win10 installation. No metadata syncrhonization (what's that?).
C1 doesn't take all the memory right away. But after I've edited a number of photos, C1 has 5GB and never gives any of it back.
5GB is about right for operational purposes these days.
Depending on how much memory you have available and how many applications are fighting over it, more than 5GB would be fine. No point in having memory and not making use of it.
Most of the photography related applications I have used over the years seem to set some sort of boundary limits on how much working memory and cache disk space they expect to use for optimal overall performance. Things like keeping in memory work undertaken earlier in an edit session so that you can get back to it quickly should you choose to do so.
Obviously there needs to be some sort of logic and balance to that but most applications will try to provide something helpful for a smooth process flow. From your earlier posts I guess you know about all of that but it is perhaps worth repeating here for others who stumble across this thread in the future.
8GB RAM may no be entirely optimal for editing larger files these days but is probably sufficient so long as C1 is not in contention with other memory hungry applications.
I rarely have any issues with C1 - though one exception was yesterday when attempting to add a layer mask made the application hang. Windows 7 in my case. A reboot fixed that.
I suspect that Firefox, which seems quite temperamental the way I use it and definitely has memory management issues, might have been at least partly responsible.
If you feel like having a look at the C1 log files you might get some idea of what is happening but I would still recommend getting the C1 Support Team's advice.
HTH.
Grant0 -
I've recently built a new workstation and ended up re-installing Win10 three times because I was getting performance issues elsewhere and couldn't work out why. But after manually telling Windows to download the Creators Update, all my problems were solved..
Running 4.2 here and mine doesn't dip above 4.8GB when creating preview files.. and it releases RAM during and after creation..0 -
8 gb is the minimum requirement for Capture One. Minimum meaning it will run and work, but it won’t be fast.
16 gb or higher is recommended.0 -
[quote="Christian Gruner" wrote:
8 gb is the minimum requirement for Capture One. Minimum meaning it will run and work, but it won’t be fast.
16 gb or higher is recommended.
That's not quite the case here, Christian. 10.2 is taking only 5 or so gigs because there is none left.
10.1.2 was managing memory fairly well; under 3GBs for most large preview generation.
I'm testing right now. 10.1.2 does 2-2.5GB. 10.2 already hit 5.2GB, came back down to 3.5 and is at 4.6 going up again.0 -
I have been having performance problems in 10.2 as well on a Windows 10 machine. Coming from version 9 to 10 the problem is with .eip files, which I have been using with no issues prior to the upgrade to 10. If you unpack all .eip files you will see a significant increase in performance. Not sure why it is different in 10 but it is.
You will also want to turn off all sync functions as well.0
Post is closed for comments.
Comments
11 comments