We have been shipping!
We have been shipping! We have something even cooler brewing though :)
6 appearances on the backlist front page in the last 30 days.
We have been shipping! We have something even cooler brewing though :)
We built a simulator to understand the performance of @tensorlake 's sandbox scheduler and dataplane during sandbox creation bursts. We can safely simulate traffic bursts without spinning up 100s of very expensive machines. Google talk
In 2016 I worked on a 1 million container challenge while working on Nomad at Hashicorp. We spun up a million containers in 5-7 minutes and keep them running for an ~hour and show our users Nomad can run large clusters at steady state. 10
We don’t kill sandboxes if connections are alive, and users are programming against that guarantee now. May be others do it too?
A few architectural choices we made for Tensorlake sandboxes are helping us move quickly now - 1. Runtime environment driver architecture on the dataplane. This lets us run CloudHypervisor, Firecracker, and gVisor transparently for differe
People are building interactive agents (in addition to background agents). The time-to-interactive (TTI) metric measures how quickly users see something from the agent. Users often just see a spinner while a sandbox spins up and installs t