CPU usage should be acceptable about gauge-python HOT 7 CLOSED

Should be fixed in nightly >= 18-04-2018

from gauge-python.

Working as expected on

Gauge version: 0.9.8.nightly-2018-04-19
Commit Hash: 58298e2

Plugins
-------
python (0.3.0.nightly-2018-04-18)

from gauge-python.

I'm able to replicate the issue using gauge version:
$ gauge -v
Gauge version: 0.9.9
Commit Hash: 8db625f
python (0.3.2)

OS:
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
VERSION="9 (stretch)"

hardware specifications : all attached
hardware_specifications.txt

After the gauge run command is run until the first test starts around 1 minute passes( during this time the processor usage is around 100% )
htop screenshot:

gauge.log :
14:34:32.871 Plugin python is already installed.
14:34:32.872 Plugin html-report is already installed.
14:34:32.872 Plugin spectacle is already installed.
14:34:32.872 Plugin flash is already installed.
14:35:43.994 # Check the item preview
14:35:46.811 ## Login with default credentials

Notes to reproduce:
The issue doesn't appear in the beginning of a new project, but after more step implementations are added. I cannot add the project i'm working on, but the issue can be reproduced starting with a new project

For example, using attached project(gauge-test.tar.gz) composed from the initial project template plus some dummy new step implementations the process needs more than 1 minute to start the tests while processor is at 100%
gauge-test.tar.gz

from gauge-python.

Considerable optimisation for initialisation is done. Execution optimisation will be handled in #79

from gauge-python.

@marius-uncrop
Thanks for reporting the issue.

This issue is about the performance issue during load. With the given project loading(project initialization) also had an issue . This has been addressed in the following version.

Gauge version: 0.9.9.nightly-2018-05-24
Commit Hash: 2150e31

Plugins
-------
python (0.3.3.nightly-2018-05-25)

As mentioned by @NivedhaSenthil, the execution optimization will be done as a part of #79.

from gauge-python.

@sguptatw , @NivedhaSenthil ,
thanks for working on this; from the initial tests, I notice a huge improvement after this task + #79 .

your work is really appreciated !!!

from gauge-python.

@marius-uncrop glad to know it worked!

from gauge-python.