Presently, the transmission of OS images from Dispatch to VMNode is not streamed. It is read into a vector and then transmitted. The problem is there must be sufficient RAM to load the entire image into memory. This severely limits the applicable image sizes.
I've hard coded a limit into Dispatch for images greater than 10G. This should avoid most situations (depending on current system loads) in which the user's system suddenly starts thrashing. It is a temporary solution that works in certain circumstances.
Solution
Take advantage of Boost.ASIO's streaming capabilities in conjunction with Boost.IOStreams compression algorithms. In this way, files can be streamed, piece by piece, from Dispatch to VMNode.
moralismercatus
commented
7 years ago
Problem
Presently, the transmission of OS images from Dispatch to VMNode is not streamed. It is read into a vector and then transmitted. The problem is there must be sufficient RAM to load the entire image into memory. This severely limits the applicable image sizes.
I've hard coded a limit into Dispatch for images greater than 10G. This should avoid most situations (depending on current system loads) in which the user's system suddenly starts thrashing. It is a temporary solution that works in certain circumstances.
Solution
Take advantage of Boost.ASIO's streaming capabilities in conjunction with Boost.IOStreams compression algorithms. In this way, files can be streamed, piece by piece, from Dispatch to VMNode.