[tjoff]

Before I tried coding agents my guess would have been: none.

But seeing how slow claude code and copilot cli are and how much ram they use I'm flabbergasted. If you have long running sessions they can both take tens pf gigabytes of ram and feel quite sluggish.

[i_am_a_peasant]

huh. my evidence with codex hasn’t been so bad. and tbh why would i discourage anyone from coding. hack away mr hacker. your solution will either sink or swim

[krzyk]

codex is in rust and not in power and memory hungry js/ts.

[i_am_a_peasant]

oh sweet I had no idea. funny that i mostly use it to write rust

[dorian-graph]

It was previously JS/TS, but they rewrote it in Rust, sometime in the past 12 months.

[manmal]

Check out its app-server, IMO it’s a decent foundation to the codex clients.

[mpalmer]

The appetite for Rust is the appetite for higher guardrails. Automatic memory management in safe Rust makes it less likely your app bloats even as its source balloons.

The people "writing" agents are not themselves experts in how to write performant code. Claude Code is so massive and ugly it can only be realistically maintained by continuing to throw LLMs at it. But that's not a replacement for good software design.

[crabmusket]

I've been playing with running Claude Code inside a Vagrant VM. I can't be certain it was getting OOM killed when I allowed the VM 4GB of RAM, but when I went to 16 it did seem to be more stable...

[yjftsjthsd-h]

> I can't be certain it was getting OOM killed when I allowed the VM 4GB of RAM

Of it's actually getting OOMed (and not backing off by itself), I'm pretty sure that's logged in dmesg. Or earlyoom or systemd-oomd if userspace is in play and getting there first.

[crabmusket]

Thanks for the tip, I will probably try shrinking it back to 4 to see, as that seems like it should be enough RAM for anybody (:

[Mjarvis]

Yes...exactly. Its frustrating and inefficient.