v9 a resource hungry demon? - Re generating previews...
A concern regarding base system requirement to effectively run v9;
Is C1P v9 a memory hog regenerating previews?
Regarding adding 600+ CR2 canon raw files to a newly created v9 catalog- externally located images to catalog.
Did a quick import (images kept external to catalog) - The system basically has frozen with the Processor running between 30-7o% usage and over 80% of RAM being used a total 20GB memory (private bytes) of RAM being used as the previews are being generated... for minutes... Unfortunately I do not have $$$ buy a new 32GB RAM system to use the program (Win7 i7 64x 8GB currently) will have to stay at v8... A Shame!
Has C1P placed itself out of the reach of the market by imposing high demands on base computing system platforms to use this otherwise great product?
I can't think of any other photo editing software that creates this load on the machine (CC, DXO, ON1, etc...).
?Or is this "merely" a teething problem being encountered by C1P's major new version being released?
A shame...
Is C1P v9 a memory hog regenerating previews?
Regarding adding 600+ CR2 canon raw files to a newly created v9 catalog- externally located images to catalog.
Did a quick import (images kept external to catalog) - The system basically has frozen with the Processor running between 30-7o% usage and over 80% of RAM being used a total 20GB memory (private bytes) of RAM being used as the previews are being generated... for minutes... Unfortunately I do not have $$$ buy a new 32GB RAM system to use the program (Win7 i7 64x 8GB currently) will have to stay at v8... A Shame!
Has C1P placed itself out of the reach of the market by imposing high demands on base computing system platforms to use this otherwise great product?
I can't think of any other photo editing software that creates this load on the machine (CC, DXO, ON1, etc...).
?Or is this "merely" a teething problem being encountered by C1P's major new version being released?
A shame...
0
-
Probably a memory leak with Canon raw files, as you can see in another thread (the:
viewtopic.php?f=62&t=21386&sid=4467097ec7c43e678f9324c0643a2d43#p100855
cheers0 -
Aah - this is definitely an issue, disappointed of course that the memory "leak" continues to affect the usage of the program. Knowing the complexity of systems and the almost infinite number of variables that can affect performance, it can be very difficult to narrow down the root causes in memory leaks - still, rather disappointed to say the least that the product is released with one of the major RAW platforms in the world not being fully compliant in the performance of the product and as I see it, this presents a significant stumbling block I believe to the potential of this otherwise excellent product.
Patiently awaiting the final solution to this conundrum...
David0
Post is closed for comments.
Comments
2 comments