VTG consumes too much CPU time
I suddenly noticed that when almost nothing from the Klever suite operates (there wasn't enough disc space to solve remaining verification tasks), VTG still occupies the whole CPU core. Perhaps this doesn't happen when everything is operating normally but I am not sure.
#3 Updated by Ilya Shchepetkov 9 months ago
- Assignee changed from Ilya Shchepetkov to Ilja Zakharov
- Status changed from New to Open
Not only VTG consumes too much CPU time, but scheduler-client as well. Some fixes/workarounds are implemented in the feature_8625 branch. Ilja, please take a look at it.
There are some other suspicious places similar to the one fixed in the branch: you can find it searching 'err_q.finished' in the sources.