Bug #8625

VTG consumes too much CPU time

Added by Evgeny Novikov about 3 years ago. Updated over 2 years ago.

Tasks generation
Target version:
Start date:
Due date:
% Done:


Estimated time:
Detected in build:
Published in build:


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.



Updated by Evgeny Novikov almost 3 years ago

Also this is the case when using VerifierCloud - VTG takes almost 2 times more CPU time than CPAchecker (and all other Core components) when solving simple tests.


Updated by Evgeny Novikov over 2 years ago

  • Assignee changed from Ilja Zakharov to Ilya Shchepetkov

Let's another Ilya will analyze the reasons of this issue.


Updated by Ilya Shchepetkov over 2 years 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.


Updated by Evgeny Novikov over 2 years ago

  • Target version changed from 2.0 to 1.0

Since Ilya already identified reasons of this issue, we definitely need to fix them in Klever 1.0.


Updated by Ilja Zakharov over 2 years ago

  • Status changed from Open to Resolved

Modified a bit but in general kept as is. The branch is the same (feature_8625).


Updated by Evgeny Novikov over 2 years ago

  • Status changed from Resolved to Closed

I merged the branch to master in 06278b90. Thanks to everybody involved. Now Klever can spend more CPU time for preparing verification tasks and for solving them.

Also available in: Atom PDF