I guess, toggling the “Scroll Locked” button “Locked” has a similar (but a bit less) effect as disabling “Log executed test steps”.
“Project Setting > Execution > Log executed test steps Enabled/Disable” option was freely available in KS v6.x, but turned to be Enterprise feature at v7.0. Users of the Free version can not disable “logging executed test steps”. See the following post for the history.
Now I have found the Scroll Lock button, which is freely available to all in v7.x and v8.0, decreases the overhead of Log Viewer.
I am glad that I could find it.
I guess, turning “logging executed test steps” disabled will decrease more of CPU overhead than setting LogViewer with “Scroll Locked”.
I have ever read the source code of Katalon Studio to find out how it logs executed steps. See this for my findings. I found that, if the option is disabled, Katalon skips logging the “START” event and the “END” event of all lines of a Test Case script. No step-execution-logging event is fired.
On the other hand, in the case where the step-execution-logging is enabled but the LogViewer is Scroll-Locked, the step-execution-logs will be fired (hence consumes some amount of CPU/memory resources) but the logging events will be ignored by Log Viewer. You know, the GUI rendering process of Log Viewer with Scroll unlocked will consume a lot of CPU.
Toggling the Log Viewer “Scroll Locked” decreases much overhead, though less than disabling the “log executed steps”. Still I believe “Scroll Locked” will help the KS Free version users who want to run long-running-tests.
@Jass the product owner of Katalon Studio
Please do not change the “Scroll Lock” button to be an Enterprise feature.