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
Each shell and filesystem interaction via dockerblade consumes at least one, and sometimes multiple, docker exec calls. The overhead of making a docker exec call is sometimes as long as 0.5 seconds, even on high-end hardware.
We should come up with an alternative approach that eliminates that bottleneck for most operations. Below are a few options:
SSH: we spawn a portable SSH server inside the container and issue commands to it via Paramiko. I suspect that this will create various networking and compatibility issues, and that it may be slightly slower than alternatives.
XMLRPC: we spawn a portable XML RPC server inside the container. This works pretty well for everything except non-blocking calls (i.e., Popen). To handle non-blocking calls, we would need to either: (a) implement our own protocol for creating, inspecting, and killing processes; or (b) fall back on docker exec for those calls (this is the best solution for now).
Each shell and filesystem interaction via dockerblade consumes at least one, and sometimes multiple,
docker exec
calls. The overhead of making adocker exec
call is sometimes as long as 0.5 seconds, even on high-end hardware.We should come up with an alternative approach that eliminates that bottleneck for most operations. Below are a few options:
docker exec
for those calls (this is the best solution for now).Methods
The text was updated successfully, but these errors were encountered: