Feature #6906

Make VTG strategies task decision requests delay configurable

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

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


Estimated time:
Published in build:


At the moment VTG strategies (actually just ABKM since Vitaly did nothing still) requests Bridge for task decisions each second. But this may be both too often and too seldom. Corresponding option should be included into a Klever Core configuration rather than in jobs since it most likely doesn't affect verification results.

Related issues

Related to Klever - Feature #8097: Decrease the number of requestsClosed04/19/2017

Has duplicate Klever - Bug #7854: Remove busy waiting from VTG strategiesRejected01/16/2017

Blocked by Klever - Feature #8299: Implement a new request to get statuses of solving tasksClosed07/17/201707/18/2017




Updated by Evgeny Novikov over 3 years ago

  • Priority changed from Normal to High

Increase the issue priority as of its duplicate. There some ideas how to solve it can be found.


Updated by Alexey Khoroshilov over 3 years ago

I have said about DBs

May be task queues should be managed using something like RethinkDB or CouchDB?
Or maybe PostgreSQL notifications would be enough?

but as far as we do not work directly with DBs, may be, approaches like EventsSource could be more appropriate to organize a channel from server to client:


Updated by Evgeny Novikov over 3 years ago

  • Assignee set to Ilja Zakharov
  • Priority changed from High to Urgent

Let's do it together with #6608.

I don't recommend to use any "advanced" technologies since this usually hardens everything and gives not so much as expected. Nevertheless next time if it will be really necessary and one will have time an appropriate time we can try.


Updated by Evgeny Novikov about 3 years ago

  • Target version set to 2.0

Updated by Evgeny Novikov about 3 years ago

  • Category set to Tasks generation
  • Target version changed from 2.0 to 0.2

This considerable Core refactoring is always completed and it would be better to have it in master ASAP while Klever 1.0 will be devoted to great conceptual improvements.


Updated by Ilja Zakharov about 3 years ago

  • Status changed from New to Resolved

Implemented in the core-refactoring branch as a part of VTG and AVTG major refactoring.


Updated by Evgeny Novikov about 3 years ago

  • Status changed from Resolved to Closed

I merged the branch to master in aec48ac1. At the moment parameters are hardcoded but one day users will be able to specify them if we will find this useful.

Also available in: Atom PDF