Startup time ...
in v8 it went up to about 2 mins for me, which is acceptable considering the application performance was better once up and running, with 8.1 it seems to be significantly longer, I haven't timed it, but I'm guessing something like 5 minutes - is this normal?
0
-
I wouldn't think that is normal.
However, Mine takes two minutes to open and I find that unacceptable.
When its open, do you find the catalog performance good?
Not just scrolling and editing but keyword search, using the keyword filters, etc.
Jimmy0 -
You made me curious, so I timed 2 Macbooks.
Mac 1: Macbook Pro 5,2 (mid 2009), 2.8GHz, 8GB RAM, 1TB HDD, OSX 10.10.1, CO 8.1
Mac 2: Macbook Pro 11,3 Retina (mid 2014), 2.8GHz, 16GB RAM, 1TB SSD, OSX 10.10.1, CO 8.1
For testing I used a 10GB local catalog with 8000 referenced images on a 2.5" USB HDD (online)
Times measured after (re-)booting to have an empty cache buffer. CO and PS not(!) open.
CO and PS were opened by double-clicking the catalog / PSD file.
Mac 1:
Opening: < 22s local catalog (online)
Keyword search: < 3s (single keyword in all 8000 catalog images)
Mac 2:
Opening: < 12s local catalog (online)
Keyword search: < 2s (single keyword in all 8000 catalog images)
Forgive me my poor accuracy. I rounded up to the next full second. 😄
And I´ve got nothing to complain about.
Regards,
Hans-B.0 -
For testing purposes (among others) you can have Capture One start without any session or catalog it had previously opened.
After clicking on the program icon, press the Alt-key and keep it pressed until the Recent dialog appears. Next, you can open your session or catalog.
This way you can determine how much time the program needs to start, and how long it takes to open the session or catalog.0 -
OK - I timed it there ... 9min 30s, albeit with a browser and audio application open. System is 2.3GHz i7, 16GB ... SSD space is always at a premium, so perhaps that's an issue. Catalog is big with 37.5K images, most of them referenced on a NAS. Using the Alt method suggested, application starts quickly, so opening the catalog seems to be the issue. General performance once the catalog has loaded is acceptable, not super fast, but OK. 0 -
i am working on my imac only with Catalog and on my Mac pro with sessions and
i found that C1 with sessions Library works slowly as with Catalog 😭0 -
I've also found opening large catalogs on startup to be really slow. Often a several minute delay. I don't remember V7 being so bad. 0 -
Has anyone found a way to improve the time to open a large catalog (besides more hardware) or got to the bottom of what causes opening a large one to be slow in v8.1? 0 -
[quote="David One" wrote:
Has anyone found a way to improve the time to open a large catalog (besides more hardware) or got to the bottom of what causes opening a large one to be slow in v8.1?
I would contact support. I know this is a wider problem... a couple of folks on another forum I frequent were complaining of multi-minute startup times with C1 opening large catalogs.0 -
What I have heard on another forum is that it may be related to the folder you have selected when you quit. For example, if you have All Images selected, it will take far longer to start up than a folder with a few images in it.
It takes roughly 22 seconds here with a catalog with just over 25,000 photos (Mac Mini Quad i7, 8GB RAM).0 -
This could well be a problem with using networked storage, what sort of drive do you have, and how is it connected to the shoot computer? I only use a NAS drive as a media server so find that I can barely get 20mb/s transfer speeds via LAN cable.
I always advise shooting to a fast external SSD, like the lacie rugged SSD or similar. That way you are not slowing down the boot drive.0 -
Same problem here. 40K images, startup time over 2 minutes. Trying to do anything in the filters panel results in a spinning beach ball for 10 to 15 minutes. Files are all local on a second HDD in my 2010 Macbook Pro (2.66 i7 / 8Gb RAM), with the catalog residing on my SSD.
I've given up and gone back to Lightroom. I way, way prefer C1, but need to have a functioning catalog.0 -
I've contacted support, but they simply suggested not selecting a large folder when quitting or better hardware. I do have masters on a slow NAS, but this is hardly ever mounted. My machine is a 2012 MBP with 16GB RAM and the catalog is on the internal SSD. The only thing I can think of is unsupported file types, or the unmounted NAS might be causing an issue .... this only became an issue in 8.1 ... 😐
CPU doesn't seem to be doing a whole lot when starting up, lots of free memory, I get a spinning wheel without text for a 8ish mins, before it goes to "Loading Capture One Library", from this point it takes about 90s0 -
[quote="David One" wrote:
I've contacted support, but they simply suggested not selecting a large folder when quitting or better hardware. I do have masters on a slow NAS, but this is hardly ever mounted. My machine is a 2012 MBP with 16GB RAM and the catalog is on the internal SSD. The only thing I can think of is unsupported file types, or the unmounted NAS might be causing an issue .... this only became an issue in 8.1 ... 😐
CPU doesn't seem to be doing a whole lot when starting up, lots of free memory, I get a spinning wheel without text for a 8ish mins, before it goes to "Loading Capture One Library", from this point it takes about 90s
Yeah, they tried to blame my hardware as well.
My machine is a 2012 Mac Pro.
Lets see, I have the catalog on a SSD mounted in the PCI Express slot with read/writes at over 400mbs.
The originals are sitting on another 1TB SSD mounted on the same PCI Express card as the first.
24GB Ram
Six core 3.33GHz
Sapphire 7950 3Gb Video card.
Oddly, Lightroom opens quickly, and is quite snappy on my old decrepit tower.
In an experiment, I moved everything to spinning drives and Lightroom slowed down just slightly.
No, the issue is simple:
The database they are using has problems, plain and simple.
It doesn't appear that Phase One will acknowledge the issues let alone resolve them.0 -
Hehe, you picked the right avatar.
C'mon now, PhaseOne accept lots of issues as bugs, and do fix them. Just sounds like this is a new one that needs some investigation. It'll get resolved. Sometimes I think a lot of the "attitude" that people get from support might actually come down to language and different European vs American sensibilities. Sometimes, especially in text, some cultures can seem more aggressive than others just by a different sentence structure.0 -
[quote="meanwhile" wrote:
Hehe, you picked the right avatar.
C'mon now, PhaseOne accept lots of issues as bugs, and do fix them. Just sounds like this is a new one that needs some investigation. It'll get resolved. Sometimes I think a lot of the "attitude" that people get from support might actually come down to language and different European vs American sensibilities. Sometimes, especially in text, some cultures can seem more aggressive than others just by a different sentence structure.
I'm not as hairy as Carl 😄
Anyway, I try really hard to see things from different perspectives. I do take differing languages in account as well.
In my particular support case which lasted several weeks, they just dropped it, or said as much.
I spent a lot of money and several hours "diagnosing" the problem, THEIR problem. So I do have some investment in the issue.
This bug is the only thing that's keeping me from using C1 instead of Lightroom.
The simple fact is that Lightroom and C1 use the same basic database: SQlite. Their is absolutely no reason why they cannot behave the same, yet they do.
Funny thing is, I still believe that C1 is heads and shoulders above Lightroom in the Raw development field, so I continue using it. I still use C1's cataloging, but not exclusively.I still import everything into LR because of its cataloging, then copy to C1. This is a waste of hard drive space, and more importantly, my time.
I do post positive things, and I try to be helpful when I can.
However, the shortcomings have to be pointed out for two reasons:
So that C1 can be improved
So that others having issues don't go "chasing the dragon" trying to resolve problems by buying newer, "better" hardware.
This is from personal experience.0 -
Yep, I know, it was just a gentle rib. I guess I've had the opposite experience with actually getting my issues solved, so I'm coming at it from a different perspective. 0 -
[quote="Jimmy D Uptain" wrote:
...
The simple fact is that Lightroom and C1 use the same basic database: SQlite. Their is absolutely no reason why they cannot behave the same, yet they do...
Jimmy, it might have something to do with the fact that the Lightroom SQLite database comprises 96 tables and 221 indexes, vs. 21 and 19 for Capture One.
It would seem that in Capture One much more functionality is handled outside of SQLite.
Cheers,
Mogens0 -
[quote="Jimmy D Uptain" wrote:
[quote="David One" wrote:
I've contacted support, but they simply suggested not selecting a large folder when quitting or better hardware. I do have masters on a slow NAS, but this is hardly ever mounted. My machine is a 2012 MBP with 16GB RAM and the catalog is on the internal SSD. The only thing I can think of is unsupported file types, or the unmounted NAS might be causing an issue .... this only became an issue in 8.1 ... 😐
CPU doesn't seem to be doing a whole lot when starting up, lots of free memory, I get a spinning wheel without text for a 8ish mins, before it goes to "Loading Capture One Library", from this point it takes about 90s
Yeah, they tried to blame my hardware as well.
My machine is a 2012 Mac Pro.
Lets see, I have the catalog on a SSD mounted in the PCI Express slot with read/writes at over 400mbs.
The originals are sitting on another 1TB SSD mounted on the same PCI Express card as the first.
24GB Ram
Six core 3.33GHz
Sapphire 7950 3Gb Video card.
Oddly, Lightroom opens quickly, and is quite snappy on my old decrepit tower.
In an experiment, I moved everything to spinning drives and Lightroom slowed down just slightly.
No, the issue is simple:
The database they are using has problems, plain and simple.
It doesn't appear that Phase One will acknowledge the issues let alone resolve them.
We are always concerned when it comes to performance, but things that might look simple to do from the outside, are not always simple from the perspective of the people doing the actual developing.
We have several areas of interest when it comes to this topic, and we will continue to improve the performance in all areas, where possible. However, it will not happen overnight, and it will likely happen in iterations, so you might not notice too much difference from one service release to another.0 -
I am told by a long time colleague responsible for developing some business analysis applications (Nothing like photo editing, except that all databases are something like photo editing in what they do) that it is relatively easy to set up a core database engine to be the equivalent of a sports car or a truck but much more complex (at best) to generate a very fast heavy load shifter that satisfies a wide range of perceived user needs.
Of course with enough investment one might buy a large truck that can move very quickly or fit a tow bar to a sports car and pull a big trailer. Both options are likely to come with their own set of new problems and complexities.
Most users are probably in the middle ground and seek something like a quickish people carrier with a small towable device from time to time. In general the elapsed journey time will be little different to either the sports car or the large truck. (Assuming reliability.)
All just my opinion of course.
Grant0 -
[quote="Christian Gruner" wrote:
[quote="Jimmy D Uptain" wrote:
[quote="David One" wrote:
I've contacted support, but they simply suggested not selecting a large folder when quitting or better hardware. I do have masters on a slow NAS, but this is hardly ever mounted. My machine is a 2012 MBP with 16GB RAM and the catalog is on the internal SSD. The only thing I can think of is unsupported file types, or the unmounted NAS might be causing an issue .... this only became an issue in 8.1 ... 😐
CPU doesn't seem to be doing a whole lot when starting up, lots of free memory, I get a spinning wheel without text for a 8ish mins, before it goes to "Loading Capture One Library", from this point it takes about 90s
Yeah, they tried to blame my hardware as well.
My machine is a 2012 Mac Pro.
Lets see, I have the catalog on a SSD mounted in the PCI Express slot with read/writes at over 400mbs.
The originals are sitting on another 1TB SSD mounted on the same PCI Express card as the first.
24GB Ram
Six core 3.33GHz
Sapphire 7950 3Gb Video card.
Oddly, Lightroom opens quickly, and is quite snappy on my old decrepit tower.
In an experiment, I moved everything to spinning drives and Lightroom slowed down just slightly.
No, the issue is simple:
The database they are using has problems, plain and simple.
It doesn't appear that Phase One will acknowledge the issues let alone resolve them.
We are always concerned when it comes to performance, but things that might look simple to do from the outside, are not always simple from the perspective of the people doing the actual developing.
We have several areas of interest when it comes to this topic, and we will continue to improve the performance in all areas, where possible. However, it will not happen overnight, and it will likely happen in iterations, so you might not notice too much difference from one service release to another.
Thanks for posting. In my scenario it got worse going from 7 -> 8 -> 8.1. With v8 it took about 2 mins to load the catalog, but overall performance was much better, so I personally thought this was a good compromise. However, with v8.1 it jumped to 10mins startup time, which is a pain....0 -
Anyone able to interpret these logs and the 8 min delay in bold?
2015-03-25 19:40:34.833 (0xb0093000) | Enabling PTP (Nikon) provider
2015-03-25 19:40:34.834 (0xb0093000) | Initializing Capture Providers
2015-03-25 19:40:34.834 (0xb0093000) | Initializing IQP Provider
2015-03-25 19:40:34.834 (0xb0421000) | Thread 0xb0421000 started [USB device refresh]
2015-03-25 19:40:34.834 (0xb04a3000) | Thread 0xb04a3000 started [USB device monitor]
2015-03-25 19:40:34.834 (0xb0525000) | Thread 0xb0525000 started [Phase One Camera Finder - notification thread]
2015-03-25 19:40:34.835 (0xb0093000) | Initializing PTP Provider
2015-03-25 19:40:34.835 (0xb0093000) | PTP Monitor - Start.
2015-03-25 19:40:34.835 (0xb0093000) | PTP Monitor - Stop.
2015-03-25 19:40:34.835 (0xb0093000) | PTP Browser - Singleton initialized.
2015-03-25 19:40:34.837 (0xb0093000) | PTP Browser - Unsubscribing an event condition : 0x7e16e460.
2015-03-25 19:40:34.837 (0xb0093000) | PTP Browser - Subscribing an event condition : 0x7e16e460.
2015-03-25 19:40:34.837 (0xb05a7000) | Thread 0xb05a7000 started [Device refresh]
2015-03-25 19:40:34.839 (0xb0629000) | Thread 0xb0629000 started [Event dispatcher thread]
2015-03-25 19:40:34.842 (0xb06ab000) | Thread 0xb06ab000 started [Event dispatcher thread]
2015-03-25 19:40:34.843 (0xb072d000) | Thread 0xb072d000 started [Event dispatcher thread]
2015-03-25 19:40:34.845 (0xb07af000) | Thread 0xb07af000 started [Event dispatcher thread]
2015-03-25 19:40:34.846 (0xb0831000) | Thread 0xb0831000 started [Event dispatcher thread]
2015-03-25 19:40:34.848 (0xb08b3000) | Thread 0xb08b3000 started [Event dispatcher thread]
2015-03-25 19:48:58.236 (0xb0115000) | Thread 0xb0115000 started [Event dispatcher thread]
2015-03-25 19:48:58.240 (0xb0197000) | Thread 0xb0197000 started [Event dispatcher thread]
2015-03-25 19:48:58.243 (0xb0219000) | Thread 0xb0219000 started [Event dispatcher thread]0
Post is closed for comments.
Comments
21 comments