- Joined
- Aug 17, 2018
- Messages
- 90
- Motherboard
- Gigabyte Aorus H370 Gaming WiFi
- CPU
- i3-8100
- Graphics
- RX 560 4GB
- Mac
no need for:How about this?
<key>Intel</key>
<true/>
using cpus=1 makes your system very slow, only to be used when booting older systems, not really required nowadaysThanks Feartech for your advice.
I removed cpus=1 (clover configuration/Boot) and Inject Intel (clover configuration/Graphic).
I tested Calendar with my routine. I got Calendar to use 180%(?) of the CPU and within a minute it had gone back to ‘zero’.
Looked good. Tried a few more times and more demanding tasks with the same success.
I noted though having changed these values the verbose boot text was different. Also the first time it did the boot got to a black screen when I would have expected the apple logo and then did the verbose boot again but with different text. Subsequent boots only did the verbose once and the normal text as had been previously. This is just an observation.
So I tested cpus=1 and Inject Intel separately and found the just deselecting cpus=1 the Calender problem that had been around for years was solved (hopefully for ever).
From my brief reading, cpus=1 is the number of cores used when booting but irrelevant afterwards. Intriguing question is why does it have an effect on Calender hogging the CPU at random? No great moment if there isn’t an answer but just curious.
Thanks again.
cpus=1 restricts your 4 core processor to a single core which unsurprisingly has a marked impact on performance.By de-selecting cpus=1 (config.plist/boot), the Calender no longer hogged 100% of the CPU
may also be worth checking over:By de-selecting cpus=1 (config.plist/boot), the Calender no longer hogged 100% of the CPU – YEH!
As Feartech says there were processes that did run a lot faster.
I installed a later version of Clover Configurator so I could get Imac 19,2 but when I selected that in SMBIOS I ended up with only one monitor out normal two working.
As mentioned previously I was getting different shutdown and start-up verbose screens with sometimes pages of errors flashing past.
Other things became evident. I run Carbon Copy Cloner routines every morning and I was finding they were failing and the various passwords needed to be reset. Later I found the CCC password file was being emptied.
When I shutdown the hack I found mostly that instead of shutting down it rebooted itself. I had to go round that loop several times but usually by the third shutdown/reboot it did shut down.
The pages of errors I got (amongst others) contained lines like this:
Bool ATIController::TestVRAM(PCI_REG_INDEX, bool) – FAILED at offset= 0x00212036*,data = 0x00000000
* same and different numbers.
When I selected cpus=1 again everything work just fine except back to Calendar hogging CPU and some slower procedures.
Unfortunately the cure, as tried, was worse than the illness so I am still looking for a solution to solve the calendar problem so would be grateful for further suggestions.