It’s really hard to say without being able to ssh into your machine and run some commands on the terminal while you are using adobe suite. One super easy to use tool (that’s worth paying for) is iStat, which is a menu bar that gives you information on CPU/RAM/Disk usage in the menu bar. That will give you a good idea what the bottle neck even is.
It’s definitely possible that there is a hardware fault here, like one, or multiple of the CPU cores aren’t being able to be used, the L1/L2 cache is messed up, there’s a fault on your bus connecting the RAM. All of that would explain your reported issues, which is a systematic slowness, independent of load, which happens on all the software you try to run. Alternatively, there could be some program you are running (or virus) which is just eating system resources, so do a restart and check activity monitor (or use iStat) and see what’s going on.
The easiest path to a fix here: go to the Apple Store and have them take a look. Otherwise, you’ll have to figure out how to run these diagnostics yourself. Good luck.
It’s really hard to say without being able to ssh into your machine and run some commands on the terminal while you are using adobe suite. One super easy to use tool (that’s worth paying for) is iStat, which is a menu bar that gives you information on CPU/RAM/Disk usage in the menu bar. That will give you a good idea what the bottle neck even is.
It’s definitely possible that there is a hardware fault here, like one, or multiple of the CPU cores aren’t being able to be used, the L1/L2 cache is messed up, there’s a fault on your bus connecting the RAM. All of that would explain your reported issues, which is a systematic slowness, independent of load, which happens on all the software you try to run. Alternatively, there could be some program you are running (or virus) which is just eating system resources, so do a restart and check activity monitor (or use iStat) and see what’s going on.
The easiest path to a fix here: go to the Apple Store and have them take a look. Otherwise, you’ll have to figure out how to run these diagnostics yourself. Good luck.