Title: How we made our OCI filesystem 47× faster

Your coworker/other account, messed it up last time you submitted it too: We made our sandbox filesystem 47× faster by deleting it https://news.ycombinator.com/item?id=48195883

> Otherwise please use the original title, unless it is misleading or linkbait; don't editorialize.

You're linkbaiting.. the opposite of the guideline

https://news.ycombinator.com/newsguidelines.html

I've found that tar processing tends to dominate the time used to do anything with standard OCI layers. I have a more efficient format (that splits apart the layer into metadata+chunks) that I'm open sourcing soon if y'all are interested in using it.

Isn't it really obvious that a user space fs will always be slow, and especially slow with small files?

I don't know the purpose of microsandbox, but such an article doesn't give me great confidence in exploring it further.

That's such a HN title!

Is anyone here using this software? How do you integrate it with your agent workflow? Do you run agents in editor (Zed, VS Code, Cursor, whatever)?

Have you tried the sync feature?

Edit: FML why is this being downvoted? At least have the decency of explaining, I'm happy to adjust my conduct but I can't do so if I don't know what I did wrong.

If your problem could be solved without FUSE, it probably should!

>Every file operation inside the VM had to bounce out to the host through FUSE

Lol, yeah that was your mistake. FUSE is a phenomenal idea but anyone who has used it knows how slow it can be.

The site is impossible for me to read due to the colors. I went to lynx and i looks like it is about a file system in a VM.

You made your filesystem 47x slower by NIHing it

it depends where you want your agent to live. inside the sandbox, start a sandbox via the CLI and run your agents/do your dev in there. outside the sandbox, you'd configure your harness to use the MCP / skill integration. here's the guide: https://docs.microsandbox.dev/getting-started/agents

if you're building a harness, the SDK provides better integration. let me know if you hit any blockers.

for sync, it's currently in the works.

I can only guess at the actions of others, but I would guess it’s because your comment is a tangent and at best only vaguely related to the featured article?

The article is really about solving a particular problem with the backend of their infrastructure. Discussion about VMs, Linux kernel syscalls, file systems (virtual, FUSE, etc) would all be relevant.

Your comment is a question about whether and how people use the software itself, which is pretty unrelated to the article.

It’s a bit like an article about Porsche identifying a particular engineering nuance in their fuel injectors, and how things didn’t work the way they thought at a low level, and how they solved it once they realized it. And then you come in with a comment about what people like to do with their Porsches. Like, sure, it involves the same company but what would that have to do with the underlying article on automotive engineering?

Combine that with a growing disdain for the insistence of certain segments of the tech scene to make everything about agentic workflows, (an echo to the constant evangelism of cryptocurrencies or blockchain in the recent past) and you have a recipe for downvotes.

People are generally sick of AI, and of people who bring AI up in every single comment thread. The downvoters may not realise that TFA is by an AI company, about an AI product, making your comment tangentially relevant, and not (strictly-speaking) an example of the behaviour they're fed up with.