I forgot we are on @computesdk's storage benchmark now! Storage is our new product, we have been dog fooding it ourselves by mounting cloud volumes backed by this backend in our CI workflows. It shares build caches across jobs to speed up builds and tests.
Founder @tensorlake, building sandbox infra for agents. Past - Built Nomad @hashicorp, AI Infra @meta, Container Scheduler tech lead @linkedin and @netlfix
- Kind of a bummer that the recent paper on Europa is predicting there is very little chance to reach the sub surface ocean easily from the surface. Wonder what the europa clipper mission find when it gets there in 2030.
- The Xerox PARC of AI?Replying to @_chenglouI was part of that team. Basically ChatGPT one year before it came out. Called LMChat and then another codename. Google was too nervous to release it and DeepMind was blocked from shipping products that could disrupt Google. I think about this a lot.
- Most bare metal server companies seem to provide AMD CPUs while hyperscalers are on Intel. Why is that? It's a problem for us because we can't restore memory snapshots of sandboxes created on AWS on AMD servers.
- We are seeing once a user builds their CI infrastructure on Tensorlake, usage keeps going up and up as they start using or building software factories. Claude and Codex are more of a limiter at this point to acceleration because they still need humans in the loop for the mostCI is one of the bottlenecks for builders shipping 100x more code today. You can now build scalable GitHub Runner infrastructure programatically on Tensorlake sandboxes, scaling out to thousands of sandboxes when PRs are updated to run tests, then scaling back down to zero!


