Same sluggish behavior in 10.2

I had my hopes up but same issues of timeline sluggishness.

Edit for an hour or so.
Drag a title, any title, to the timeline.
Release title where you want to to be placed.
Title hangs there for about 2 seconds, a quick beach ball loads for about 1/4 of a second, then the title drops in place.

this is what I am seeing anyway.
At this point my memory has increased to about 1/3 registered as active. (from 32gigs ram)

Try running FCP X using a new admin user account.
I bet you'll be surprised at how speed it is.

Very often problems are related to settings, caches, login items, etc.
If it works well in a new account, then you'll know it is something in your own account.

I've had the exact opposite experience. Updated Yosemite and FCP X to 10.2 and wow, my 2011 iMac feels like a new machine. Before when stabilizing clips I usually did something else while waiting for analysis and rendering. Yesterday I could barely look away from the screen during rendering, even on complex scenes. Analysis is also greatly improved. And I'm editing 4K footage. Consider me impressed.

If I understood correct dkag7's problems did not start with 10.2.
It seems that for people who had FCP X working correctly, the update makes things faster in general, but I as wrote in my previous post I think dkag's problems originate somewhere outside the application.

Later today or tomorrow I will try on a fresh yosemite install with nothing else on the system

I did this before with 10.1.4 but did not notice too much of a difference having a bloated OS with a lot of applications and 3rd party plugins vs the clean install (OS and FCP)

Maybe this one will be different..?

Sometimes the problem is that people do a clean install and immediately import all the stuff in their user account. If that was where the problem was before...

As I wrote before, maybe you don't need to go as far. Try a new user first, and only do the clean install if that does not work.

I needed the clean OS anyway.

Running this test showed a mixed blessing.
It shows that fcp can run on a messy OS with a million plugins just as good/bad as on a clean install (OS and FCP) Nothing else installed.
So this means any sluggishness is either in FCP or hardware/drivers.

5,1 mac pro
680 gtx video card 2 gigs vram (tried nvida and default drivers)
3.33 6 core and 32 GB ram.

Hey Dkag7,

Since you already tried a clean install, can you tell us a bit more about your workflow?

What type of media are you using?
Are you working with a managed library or referenced media?
On what device is the media stored?

Kind regards,
Martijn

Sure,

For media, I have tried AVCHD by itself, but usually convert it on import to 422 or 422 light.

Usually I will keep the media withing the library, I have edited also via reference, but for the most part I try to keep it contained in the library.

For larger media projects, I keep the media on a 12TB external raid connected via esata (right now I am doing some tests and trying USB3 to see the speed differences) USB3 seems a bit faster but both are in the range of 200MB read/write. Media for the most part is 1920 (video), various stills and heavy on titles on a lot of my projects. For titles they are native and ones I create in motion. Some of them are in depth (filters that have titles in them/ drop zones etc..) this goes as well for custom trans/effects/generators etc.. All these effects do not always get used, but are of course still contained within the effects/titles/trans/etc.. browser area of FCP.
On the new OS I made, there are no custom effects/trans/etc.. Just the native install of the OS and FCPX.

As well I have an internal SSD raid (1TB total) where I will create libraries on for small projects. These libraries will always contain all the media on the SSD.

I have still not tried 10.2 yet on the clean OS, but if this version is like the last, there wont be that much of a performance change. It did run better, but the gains I got were not worth the new install and SSD work setting it all up. (New OS and FCPX install is on SSD as well, different from the media SSD).

To describe its sluggishness with repeated behavior, it is this:
Edit a project (422 or AVCHD)
start adding in some stills and titles
Start editing for about .5 to 1 hour.
Cuts/trims/copy and paste/titles, delete stuff, a couple tracks, etc.. Work the app like a normal edit.
Using no 3rd party plugins.
The total duration of the timeline does not need to be long (10 minutes is plenty)
During this time, if you have it, watch your memory usage rise.
Once you get to about 1/3 or so of your free memory used (in my case I have 32GB total) the sluggishness will start.
(as I posted earlier), drag a title to the timeline, let it go, and there is a 2 second delay before the title drops in place. - Trim and let go, more delays waiting for the trim to 'finish'
Play, and the scrub bar wont start moving for a second or so.
Skimming begins to fail, there will be no skim bar at all until I click off FCP and on to the desktop, then back onto FCP to re-enable it.
Contextual menu gets slow to load, changing filter settings starts sticking (by this I mean the actual movement of sliders and its live update in the viewer)
Some examples...
These are all repeatable.

I should add that previewing effects and titles in the effect browser can cause memory to rise.
This amount it rises, does not get released once clicking on another area of the app, it should.
(this happens over time during editing, previewing effects etc..)
The act of editing itself will cause memory to rise as well and this is normal, to a point.
I think I can safely say I while editing in FCP, I have never seen the memory decrease.
What i mean by this, is that if it rises for any reason (complex title/filter playback etc..)
It should release that memory, all of it, after the complex playback is over.

Also note the amount of memory you have before you open FCP from a fresh boot, let it rise as it does until things get sluggish and you need to close FCP. When you close FCP note the memory again, it will not be the same amount free before you opened FCP for the 1st time after a fresh boot.
I have not tried the memory rise issue yet in 10.2 on the new OS, but i am seeing it in my 'normal' OS.
Sluggishness happens as the memory rises, for whatever the reason..
For what ever the reason, memory does not release while in FCP and does not release 100% when FCP is closed.
This is a classic memory leak and I am pretty sure this is the entire reason for any sluggishness at all.

thanks
kurt