Birbla

Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

Sign in
  • Hacker News
  • Very similar to Google Ax, looks like it's Deepseek answer to Google
    by cloudengineer94
  • Is this like agent substrate?
    by throwaway7783
  • Appears to be similar to what Google is building with ax https://github.com/google/ax
    by erulabs
  • 12 sandboxes per code is insane, I wonder how many of these sandboxes are idle at a time. Depending on the tasks assigned the resource requirements are different. Compare an agent doing pdf conversion and one responding to a simple question. One is cpu bound the other is mostly network wait.

    This is an interesting problem from infra perspective since you cannot predict the workload. On a bigger scale you may get away with forecasts.

    Im waiting for tech that elastically allocates cpu/mem without restarting a container.

    by piterrro
  • >"Within one scale unit, the platform spans nearly 160 CPU nodes with 30K cores and ∼250 TB of DRAM. It manages petabytes of layers and images. On a typical day, a single scale unit serves about 3 M sandbox instances, with peak concurrency reaching ∼380K and a creation rate exceeding 5,000 instances per second."

    Impressive numbers!

    Whoever would have thought (in prior years) that in 2026 AI Agents (not people or corporations, at least not directly) seem to be (or seem to be rapidly becoming) the biggest consumers of cloud computing resources...

    Anyway, a very interesting paper and environment!

    by peter_d_sherman
  • 380.000 concurrent sandboxes on 160 Epyc based server nodes. Crazy stuff
    by vblanco
  • As models get better, safe-and-secure sandboxes/environments are going to be the way forward. With the recent rise in cases where models can somehow gain access to the internet and blast past the sandbox, it's very important to have all the resources contained within the sandbox with no access to the outside world.

    DSec is a good step in this direction!

    by samayashar
  • It seems every DeepSeek paper/patent has a huge number of authors, and this one is no exception. They couldn't even fit everyone on the page, there are 31 others not shown. This could be an asset protection strategy (i.e., human assets). Imagine if there were only 3 authors. Those authors may get hired away by competitors. If you list every employee on every paper then competitors don't know who to lure away.
    by flowerlad

Explore Birbla archives