Log Viewer slows down your tests. How to prevent it?

Tips and Tricks
,
2

How much memory is used? how much CPU is occupied?

When I execute the Test Suite TS1 , how much memory is used? how much CPU is occupied? I wanted to examine this.

I used a profiling tool VisualVM and had a look.

The conditions are:

  • Machine: MacBook Air (Retina, 13-inch, 2018)
  • Processor: 1.6 GHz Intel Core i5
  • Physical memory: 16 GB
  • OS: macOS Monterey v12.0.1
  • Katalon Studio: v8.2.0
  • JVM arguments in the katalon.ini :
    • XX:+UseG1GC
    • XX:+UseStringDeduplication
    • Xms256m
    • Dfile.encoding=utf-8
    • Xmx2048m
  • VisualVM versioin2.1.1
  • run the TS1 with “case 1” settings of Log Viewer

memory

Let me enumerate what I observed.

  1. The Heap size stayed under 821 MB.
  2. The size of used heap moved in the range of 240 MB - 700 MB. The Garbage Collection mechanism was working properly. The heap used by Katalon Studio’s Log Viewer is well managed.
  3. The CPU usage went in the rage of 15 % - 30 %. It seemed it would not blow up to 100 %.

Even if the TS1 repeated calling the printID for 5000 times, 16000 times or more, I suppose CPU and memory usage by TS1 will be the same. I think that Log Viewer is not guilty for memory usage.

Additionally I tried the case 9 (Log Viewer is detached & closed) with VisualVM. I saw that CPU usage went in the range of 15 % - 30 %, but the test finished far quicker.