Organizing keywords in catalog slow and high memory usage
Trying out 9.0.1 now for the first time with a converted version 8 catalog and the keyword library feature, I just ran into a first issue.
Catalog size: 39987 images
Catalog stored on internal SSD on rMBP.
I added two new keywords in the library (it still doesn't automatically populate it based on existing keywords) and then dragged on keyword onto the other keyword to group them.
Result of that was beach ball for ca. 5 minutes and C1 starts eating memory (one time up to 14 GB, second time less).
For a while there was a dialog showing that it was updating keywords, so I assume it went through all images of the collection, checked if the sub-keyword was set and then also assigned the parent keyword for those images that matched. If that assumption is correct it would mean that it took ca. 0.5 second for each image.
I'll try to summarize my results in a support ticket now.
Anyone else having this behavior?
Catalog size: 39987 images
Catalog stored on internal SSD on rMBP.
I added two new keywords in the library (it still doesn't automatically populate it based on existing keywords) and then dragged on keyword onto the other keyword to group them.
Result of that was beach ball for ca. 5 minutes and C1 starts eating memory (one time up to 14 GB, second time less).
For a while there was a dialog showing that it was updating keywords, so I assume it went through all images of the collection, checked if the sub-keyword was set and then also assigned the parent keyword for those images that matched. If that assumption is correct it would mean that it took ca. 0.5 second for each image.
I'll try to summarize my results in a support ticket now.
Anyone else having this behavior?
0
-
Don't have that exact issue though, I am having C1 Pro 9.0.0 crashing sometimes when attempting to add a child keyword to an existing entry in a shared keyword library. 0 -
[quote="NNN635434842059630093" wrote:
Don't have that exact issue though, I am having C1 Pro 9.0.0 crashing sometimes when attempting to add a child keyword to an existing entry in a shared keyword library.
That should be fixed in 9.0.1. I noticed it in the release notes. I think what I saw is mostly being caused by the way how keyword handling in the the sql database has been designed.0 -
Yes, exactly the same issues here even after updating to 9.01 - the memory leak seems much better and overall seems more stable but any activity with keywords slows down to a crawl and soaks up all available memory. Catalog 39K internal SSD 16Gb RAM 0 -
[quote="NN635115164314618060UL" wrote:
any activity with keywords slows down to a crawl and soaks up all available memory. Catalog 39K internal SSD 16Gb RAM
Happened again to me yesterday when trying to fix a typo and rename a keyword in the keyword library. Unresponsive app for minutes. Does this only happen with converted C1 8 catalogs or also with new large C1 9 catalogs? Don't understand how this was able to pass QA and get released.0 -
Same issues here.
When I try to move a keyword onto another one to create a hierarchy, C1 does not respond anymore and needs to be restarted.0 -
[quote="ApoFenomeno" wrote:
Same issues here.
When I try to move a keyword onto another one to create a hierarchy, C1 does not respond anymore and needs to be restarted.
Force quiting the application is risking your database. Just wait. Depending on the total size of the catalog it can take many minutes.0
Post is closed for comments.
Comments
6 comments