El Capitan running slowly?

John Krtanz, I appreciated your input here, and you always have to ignore the forum "police" and busybodies in favor of those contributing something useful.

Hopefully, we'll get more input as Google indexes the newer comments. It's how these posts are found to begin with, so whether they were posted 15 months ago or yesterday, if the problem is relevant, it shouldn't matter.

I'm still struggling with my situation, and hopefully someone may come along with some insight - and hopefully in less than 15 months. ;-)

Try disable and reenable Spotlight. Works like charms for me.

Thanks, Did you do this by deselecting all the categories and also deselecting the "allow spotlight to suggest"?
That's the only way I can see to "disable". Did this and also did a restart. Will see how this works throughout my work day.

Kurt Triffet wrote:

John Krtanz, I appreciated your input here, and you always have to ignore the forum "police" and busybodies in favor of those contributing something useful.

Hopefully, we'll get more input as Google indexes the newer comments. It's how these posts are found to begin with, so whether they were posted 15 months ago or yesterday, if the problem is relevant, it shouldn't matter.

I'm still struggling with my situation, and hopefully someone may come along with some insight - and hopefully in less than 15 months. ;-)

This is unbelievable. It has been suggested to you and others here how to get focused individual help in this community. But you continue to resist, for what reason only you know.

Instead of hoping someone comes along why not follow the advice provided and initiate a request for assistance instead of hoping? Read this for further guidance regarding using this community Writing an effective Apple Support Communities question

BobTheFisherman wrote:

This is unbelievable. It has been suggested to you and others here how to get focused individual help in this community. But you continue to resist, for what reason only you know.

Instead of hoping someone comes along why not follow the advice provided and initiate a request for assistance instead of hoping? Read this for further guidance regarding using this community Writing an effective Apple Support Communities question

No, it isn't unbelievable:

Just about every other 'help' forum I have ever used actively DISCOURAGES creating a new thread for every individual complaint or request for help, for the following reasons:

1.) Chances are one person's solution will help hundreds of other people: If they have to search 4,926 threads of individual requests from people who have the same problem, that is ridiculous! On the contrary, if they find one thread with several hundred posts - the majority saying "thanks - that solved it for me" with 3 or 4 solutions in the same thread, that's awesome for folks like me 🙂

2.) It clutters up the database and makes a search virtually impossible: Most search engines are based upon the number of comments in a thread and how 'popular' that particular thread is.

3.) Chances are the helpful people will soon get very tired of writing the same reply, time after time, on hundreds of different threads, and will stop responding.

I'm sure there are lots of other reasons, but I find this forum the most patronising, unhelpful, humiliating experience I have ever had on the Internet... I'm sure your little clique of geeks who only respond if we do things exactly how you think they should be done, won't miss me, but I'm out of here - life's too short for this crap... MacRumours seems much more friendly and helpful 😉

Spot on, but as mentioned, just ignore those who aren't providing anything useful.

According to your opinion ?

Vapresto wrote:

BobTheFisherman wrote:

This is unbelievable. It has been suggested to you and others here how to get focused individual help in this community. But you continue to resist, for what reason only you know.

Instead of hoping someone comes along why not follow the advice provided and initiate a request for assistance instead of hoping? Read this for further guidance regarding using this community Writing an effective Apple Support Communities question

No, it isn't unbelievable:

Just about every other 'help' forum I have ever used actively DISCOURAGES creating a new thread for every individual complaint or request for help, ...

Perhaps, but that's not the way this one works. That is one reason for writing the User Tip — so that people can effectively utilize this resource to their best advantage.

1.) Chances are one person's solution will help hundreds of other people:

Correct. That's another reason for writing the User Tip. That concept is so fundamental to this support resource that I labeled it Step 0. The number of participants who solved their problems by following that one step is incalculable.

2.) It clutters up the database and makes a search virtually impossible:

That is not correct. Search works quite well on this site. The results can be sorted by "Answered questions" if you so choose. It certainly comprises an enormous database but "cluttered" is more descriptive of this Discussion than it is the entire database of open or answered questions.

That is yet another reason for posting your own Discussion.... which you haven't done either.

3.) Chances are the helpful people will soon get very tired of writing the same reply,

That's not correct either. In fact several helpful people repeatedly suggested posting your own Discussion. You have chosen to ignore them.

to quite a few here:

Have you done the basics: when its slow, open activity monitor and look (over a period of time) at what processes are chewing up processor time and cycles?

That's one simple way to find the culprit.

Similarly look at RAM usage, although i believe several said that "looked ok".

G

John, can we please try and avoid this pointless "I need to get in the last word" type of discussion on something that has nothing to do with the OP?

If you have some knowledge about what might be causing our system lags, please chime in. Otherwise, best to move on to a thread with your area of specific expertise.

Kurt Triffet wrote:

John, can we please try and avoid this pointless "I need to get in the last word" type of discussion on something that has nothing to do with the OP?

If you have some knowledge about what might be causing our system lags, please chime in. Otherwise, best to move on to a thread with your area of specific expertise.

Try to avoid telling others where to post, that is not in your purview.

Kurt Triffet wrote:

John, can we please try and avoid this pointless "I need to get in the last word" type of discussion on something that has nothing to do with the OP?

The OP? He's long gone.

That's the point. And, you don't get it.

Thanks Grant, not seeing my computer running anything differently than it did with 10.6.8.
I "turned off" Spotlight and that seems to speed things up a tiny bit, but not enough to do any real good. Spotlight is not something I've ever found useful, so I'll keep it off.

I did run EtreCheck again. Peformance is continually excellent.

A few comments.

1) if this is a very new install, el cap moves a bunch of files around and consequently spotlight is very power intensive for a period - many minutes to hours or even > day maybe depending on the size of your affected files

2) i cannot prove this but there appears to be a learning curve to something - file optimization, etc - and my CPU usage has declined consistently over a period of many weeks

G

Thanks Grant, that makes more sense as to what might be going on. It's been a few weeks now, and I have seen a gradual improvement from the initial install, though El Capitan is not as robust on my machine as Snow Leopard was. I do think that all users coming from more than one OS behind (I was two) should do a fresh install of system and all apps to avoid these kinds of problems. My workload and amount of applications prevented me from doing this due to time constraints, but I do think that the only real solution for getting El Capitan to run at its optimum will be a drive wipe and new install.

It's workable as it is, so I'll take the path of least resistance.