You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The slowest part of COT is the actual file I/O [citation needed], especially when untarring and retarring an OVA file is required. This makes multi-stage operations like the following somewhat slow since the file is re-written and re-read repeatedly:
While COT is explicitly designed around separation of actions (so that the params defined for "edit-hardware" do not conflict with the params for "add-disk", etc.), it would be nice to provide for some mechanism of batching operations together with only a single "read" at the beginning and a single "write" at the end.
The text was updated successfully, but these errors were encountered:
The slowest part of COT is the actual file I/O [citation needed], especially when untarring and retarring an OVA file is required. This makes multi-stage operations like the following somewhat slow since the file is re-written and re-read repeatedly:
While COT is explicitly designed around separation of actions (so that the params defined for "edit-hardware" do not conflict with the params for "add-disk", etc.), it would be nice to provide for some mechanism of batching operations together with only a single "read" at the beginning and a single "write" at the end.
The text was updated successfully, but these errors were encountered: