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 <[email protected]>
Gerrit-Reviewer: Adam Litke <[email protected]>
Gerrit-Reviewer: Allon Mureinik <[email protected]>
Gerrit-Reviewer: Antoni Segura Puimedon <[email protected]>
Gerrit-Reviewer: Dan Kenigsberg <[email protected]>
Gerrit-Reviewer: Federico Simoncelli <[email protected]>
Gerrit-Reviewer: Francesco Romani <[email protected]>
Gerrit-Reviewer: Martin Sivák <[email protected]>
Gerrit-Reviewer: Michal Skrivanek <[email protected]>
Gerrit-Reviewer: Nir Soffer <[email protected]>
Gerrit-Reviewer: Saggi Mizrahi <[email protected]>
Gerrit-Reviewer: Yoav Kleinberger <[email protected]>
Gerrit-Reviewer: [email protected]
Gerrit-Reviewer: oVirt Jenkins CI Server
Gerrit-HasComments: No
_______________________________________________
vdsm-patches mailing list
[email protected]
https://lists.fedorahosted.org/mailman/listinfo/vdsm-patches

Reply via email to