etresoft wrote:
There is a big discrepancy here. You are running EtreCheck complaining about poor performance. Yet when you told EtreCheck why you were running it, you said "No problem - just checking". So which is it?
Thank you for your response!
Yes, sorry, I'm not a well-versed EtreCheck user, so for my first attempt, I thought I'd choose an option that was more "general." However, I did write in another post that there were issues with things lagging, certain programs freezing with me having to "force quit" (as EtreCheck states in the first log: "There have been numerous app crashes"), as well as issues with programs like Logic Pro and DaVinci Resolve being quite slow, having latency issues, and crashes, in a way that I would not expect to see in a MacBook Pro M1 Max with 32GB of memory.
I didn't think there'd be an issue on what I chose in the dropdown menu in EtreCheck. The later tests I did, I specifically chose "Computer is too slow," but it still seemed to do the same tests as when I chose "No problem - just checking," so thought it wouldn't matter. Please do correct me if I'm wrong.
Your EtreCheck shows no hardware problems. Your hard drive speeds are good. When you have that accompanied by a slow runtime, it means that there are some other bottlenecks somewhere in the system that may be adversely affecting your experience. I say "may" because EtreCheck really exercises lots of low-level operations. As a side effect, if there is any otherwise unnoticeable problem, then it might show up because EtreCheck is hitting those subsystems so much.
...
If you aren't have problematic incidents, then you probably don't need to be running EtreCheck. But if you do anyway, please don't erase the hard drive or anything based on the results of a report that you generated just after restarting.
Thank you for this information, this is very good to know. As I mentioned above, the issues I've had were what led me down the path to picking up EtreCheck and doing a test. I'm not planning on erasing my hard drive, but didn't want to just sit there and assume everything will fix itself on its own. These are issues that I've had for some time now. So, I thought it'd be best to actually try to figure out what is causing the issues and how I may start to understand how to ameliorate the situation. If things are looking good overall, that is good to know. And those things that are causing these bottlenecks in the system, it's great to also have a better understanding of what they are and how I can move forward with that information. Already with the feedback I've received here, I have a better idea of what to do already.
And lastly, you have lots of audio plug-ins installed. I'm not sure what's going on with those. People who have audio plug-ins either have 3 of them, or 9,223,372,036,854,775,808 of them, with little in-between. They seem to have a detrimental affect on your overall EtreCheck runtime. They probably also have a detrimental affect on your user experience, because if that is slowing down EtreCheck, it is probably showing down other operations too. I'm not sure what's going on here, but something's going on.
It's kind of like those people that complain that Apple charges too much for 8 TB hard drives. Do they really need 8 TBs of data in their home directory? Are they ever going to access all those files? Same for these plug-ins. There simply aren't that many sounds. I might just remove them from EtreCheck altogether, or just show the count.
Yes, it depends on the artist. Some people just need to have tons of plugins, but it often doesn't make sense if you're a solo artist, where you can whittle it down to your most used. In my case, I tend to work with a lot of different artists (who all work with different kinds of "fave" plugins) and a lot of different projects in both the audio and video realm. As I wrote in another post, a lot of these are necessary for compatibility.
Again, I admit that it's true that I can reduce a chunk of them, but overall, there'd still be a lot of plugins that would need to be kept on the system. Certain projects are ones that need to get updated frequently (touring productions of projects that have several lives, for instance). When I open the projects up, some of the plugins need to be in place for further edits and so on.
In any case, aside from your own aversion to having 9,223,372,036,854,775,808 plugins, are they a major culprit in the "poor performance" results of EtreCheck?
