5 ms·

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. I

by tjoff 5mo ago

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 5mo ago
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 5mo ago
  codex is in rust and not in power and memory hungry js/ts.
  - i_am_a_peasant 5mo ago
    oh sweet I had no idea. funny that i mostly use it to write rust
    - manmal 5mo ago
      Check out its app-server, IMO it’s a decent foundation to the codex clients.
    - dorian-graph 5mo ago
      It was previously JS/TS, but they rewrote it in Rust, sometime in the past 12 months.
adabsurdo 5mo ago
[dead]
Mjarvis 5mo ago
Yes...exactly. Its frustrating and inefficient.
crabmusket 5mo ago
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 5mo ago
  > 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 5mo ago
    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 (:
mpalmer 5mo ago
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.

by tjoff 5mo ago

i_am_a_peasant 5mo ago

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 5mo ago
codex is in rust and not in power and memory hungry js/ts.
- i_am_a_peasant 5mo ago
  oh sweet I had no idea. funny that i mostly use it to write rust
  - manmal 5mo ago
    Check out its app-server, IMO it’s a decent foundation to the codex clients.
  - dorian-graph 5mo ago
    It was previously JS/TS, but they rewrote it in Rust, sometime in the past 12 months.

adabsurdo 5mo ago

[dead]

Mjarvis 5mo ago

Yes...exactly. Its frustrating and inefficient.

crabmusket 5mo ago

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 5mo ago
> 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 5mo ago
  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 (:

mpalmer 5mo ago

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.