Extreme slowness in step3 Capturing keyword times metrics, sometimes

[pianofab]

Since it is such a great tool, I added robotframework-metrics as one of the steps in our internal RobotFramework test process.

This has worked great in the past, and now someone who is running our tests iterating them 100 times has discovered that sometimes the step 3 below is extremely slow, in some of the iterations.
 

{"log":"INFO: 1 of 4: Capturing suite metrics\n","stream":"stderr","time":"2024-12-11T00:32:05.756805415Z"}
{"log":"INFO: 2 of 4: Capturing test metrics\n","stream":"stderr","time":"2024-12-11T00:32:05.757776706Z"}
{"log":"INFO: 3 of 4: Capturing keyword times metrics\n","stream":"stderr","time":"2024-12-11T00:32:05.758546344Z"}
{"log":"INFO: 4 of 4: Capturing details\n","stream":"stderr","time":"2024-12-11T00:55:27.522866812Z"}

One of our test runs takes little time (like one minute or two) so this is impacting the overall execution.

We could investigate some more if you are interested... we are using the latest 3.7.0.

[adiralashiva8]

Thanks for reporting issue.
In latest version we have added few more stats in keyword metrics. This may be causing delay

We have couple of work-arounds to handle slowness:

Option 1: Exclude keywords of specific libraries using --ignorelib flag, which accepts list of library to exclude
Ex: following are default libraries excluded

IGNORE_LIBRARIES = ["SeleniumLibrary", "BuiltIn",
 "Collections", "DateTime", "Dialogs", "OperatingSystem"
 "Process", "Screenshot", "String", "Telnet", "XML"]

Option 2: Exclude keyword times in report --showkwtimes flag is True by default
Ex:

robotmetrics --showkwtimes False

it would be great if we found solution for slowness. PR are welcomed!