Closed edigaryev closed 3 months ago
Should we just put worker.updateWorker
on a separate goroutine?
This change doesn't seem make syncVMs
async which seems to be a cause of #161.
Should we just put
worker.updateWorker
on a separate goroutine?
Technically we could, but this kinda goes against the idea of having a lightweight main loop and long-running async operations that we poll from that loop.
Note that this change also prevents the blocking of service for other VMs in syncVMs()
, but if we were to only make the updateWorker()
async, that would not be solved.
This change doesn't seem make
syncVMs
async which seems to be a cause of #161.
Could you elaborate on why?
Resolves https://github.com/cirruslabs/orchard/issues/161.