Why is cocatalogdb so slow on 150000 images?

Permanently deleted user

• 2021年11月26日 11:36

 

I have around 150k images in my catalog. As someone who has a lot to do with database applications professionally, I am very surprised at how long it takes, for example, to search for images in CaptureOne. For example, if I set a filter for all 150,000 images by searching for a certain keyword, the search can take from many minutes to hours. Even a well-indexed sqlite database could perform this action in a few seconds. 150,000 entries are relatively few entries for databases if they are well indexed.

 

Why is that with Caputre One?

Does the *.cocatalogdb format work with indexes?

Has anyone else had similar experience with catalogs of similar size?

2

• 

  ernst.w

  • 2021年11月26日 21:30

  Every user of the Windows version has same experience with C1 database. This is a knows issue for years but got very better with last update. You don't need to put 150.000 images in a catalog; 30.000 aree way enough. ;)

  Capture One knows about and suggests officially not to use more than 10.000 to 15.000 images per catalog.

  (Nice joke for a photographer, I know - but does Capture One?)

  0
• 

  SFA

  • 2021年11月26日 23:06

  I could perhaps see the reason for having a very large catalog but not the need to use it all of the time for new editing.

  I could not imagine having a large number of images in a very active catalog without considering whether a full dedicated document management system for finished images might not be a better and more commercially viable option for such an archive.

  0
• 

  Permanently deleted user

  • 2021年11月27日 08:59

  The point is, why should you limit yourself if even several million photos would technically not be a problem? In order to be able to use the full strength of the filters and the keywording, for example, it makes sense to have all images in one catalog. For example, you can search for all images with the keyword "tree" without constantly having to change the catalog.

  In my opinion, catalogs are nothing more than better folders. And that's not the reason why I like to use database-supported software like Capture One ;)

  The image processing functions in Capture One are excellent, but the file handling (which should actually be a core function) is from the Stone Age and should urgently be revised, we would all benefit from it.

  0
• 

  Permanently deleted user

  • 2021年11月27日 13:51
  • 編集済み

  

  The point is, why should you limit yourself if even several million photos would technically not be a problem?

  It's rather a moot point - clearly there are "technical" reasons why Capture One struggles with overly large catalogues, which is why Capture One has long been very clear about keeping things smaller and more manageable.

  You're expecting something from Capture One which it is unable to deliver; which it is known not to be able to deliver; and which is clearly spelled out by the company as being something that you shouldn't expect it to deliver.

  we would all benefit from it.

  To those of us who take Capture One's caveat to heart, no. It's an irrelevance, because we work with Capture One the way we're advised to work with it.

  Choose to plough your own furrow by all means, but don't assume that we're all in this together, because we aren't.

   

  0
• 

  Permanently deleted user

  • 2021年11月27日 15:32

   

  Perhaps it would be correct to say that Capture One does not want to deliver here. There are hardly any technically insurmountable hurdles.

  And even someone who keeps to the limit of 10,000 images per catalog should benefit from a database that is many times faster.

  0
• 

  Frank Eigenbrod

  • 2021年12月07日 12:59

  In all honesty, I can't understand why members of the community defend this untimely behavior of the software and the limitations that come with it. Andreas Kern got to the point and the solution should be trivial according to the rules of application development: indices.
  It works everywhere, in 30 years of experience with really large databases, I've never seen it not work, so why should Capture One of all things fail?

  2

投稿コメントは受け付けていません。