Tips on How to Fix or Help a Very Laggy and Slow Keyboard Maestro?

[martin]

@sursur

I do use found images, a lot actually, but they are important to my macros and impossible to get around. It sounds like the more images used the higher the possibility of making the editor lag. It's odd the actual macro being used won't lag but the editor will with a found image. I will keep this in mind going forward and try to use the smallest images possible but since I basically already do that and since using these are important there's not much I can change there.

Peter has mentioned elsewhere that hiding the condition and found image actions will help:

Note that the Keyboard Maestro editor will implicitly be running macros if you are displaying a macro with conditions in the editor, so quitting the editor when not in use is a good idea - but just hiding it will be sufficient, since it only updates the action condition results if they are visible on the screen.

Ways to reduce KM energy consumption?

No. Keyboard Maestro will use negligible CPU & Energy as long as it is not executing a macro. You can have pretty much any number of macros available to be triggered and it will not use any appreciable CPU except when you are actually running a macro. There are a couple exceptions to this, but they would apply generally only when you have a badly behaved device attached. For example, if you have any MIDI triggered macro, and you have a MIDI device that is sending an endless stream of MIDI ev…