Nir Soffer has posted comments on this change.
Change subject: schedule: Introduce scheduling libary
......................................................................
Patch Set 4:
Francesco, I don't see how concurrent.futures (https://docs.python.org/3/library/concurrent.futures.html) is related to the scheduler. This is more related to the thread pool.
The main feature of future is waiting for future result. So you need waiting thread waiting on the future, while another thread run the operation. This means that you could run the original operation in the waiting thread. It seem to be useful when one thread is waitting for many threads to finish.
But in our case we want to have 100's of sampling objects, all running in the same thread. They are not waiting on anything, but keep the sate of the current and the next calls, and schedule themself to run the next call on the threadpool.
--
To view, visit
http://gerrit.ovirt.org/29607
To unsubscribe, visit
http://gerrit.ovirt.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: Ie3764806d93bd37c3b5924080eb5ae4d29e4f4e0
Gerrit-PatchSet: 4
Gerrit-Project: vdsm
Gerrit-Branch: master
Gerrit-Owner: Nir Soffer
nsoffer@redhat.com
Gerrit-Reviewer: Adam Litke
alitke@redhat.com
Gerrit-Reviewer: Allon Mureinik
amureini@redhat.com
Gerrit-Reviewer: Antoni Segura Puimedon
asegurap@redhat.com
Gerrit-Reviewer: Dan Kenigsberg
danken@redhat.com
Gerrit-Reviewer: Federico Simoncelli
fsimonce@redhat.com
Gerrit-Reviewer: Francesco Romani
fromani@redhat.com
Gerrit-Reviewer: Martin Sivák
msivak@redhat.com
Gerrit-Reviewer: Michal Skrivanek
michal.skrivanek@redhat.com
Gerrit-Reviewer: Nir Soffer
nsoffer@redhat.com
Gerrit-Reviewer: Saggi Mizrahi
smizrahi@redhat.com
Gerrit-Reviewer: Yoav Kleinberger
ykleinbe@redhat.com
Gerrit-Reviewer: automation@ovirt.org
Gerrit-Reviewer: oVirt Jenkins CI Server
Gerrit-HasComments: No