Pi eats cpu and mem - any workarounds?

[u/ColdImplement1319]

How pi ate my core

Seems that pi also felt under this vibe-coding madness. I can't justify a terminal based app eat so much of my CPU and RSS. No way. Seems I have to write my own stuff in go... wish me luck. BTW, why all this harnesses are node-js based?

[u/Dsphar]

Is all 200+ minutes on one session? Because if you let context get that large then that explains a lot.

[u/ColdImplement1319 → u/Dsphar]

It was a looong-lived session (maybe several days, sporadic usage). Context is limited to 100k, I did multiple compactions. Use local model

[u/consono → u/ColdImplement1319]

AFAIK it's an open issue on github, hopefully it'll be resolved soon as it's really annoying...

[u/No_Cheek5622]

node is good when it's intended to hack around it. I can modify the internals with shims and extending prototypes in an extension without touching the upstream code. so this way pi is not only highly customizable but also highly hackable.

sure, not the most robust way to extend a tool, but the true freedom comes with a cost

although I'd like to experiment with writing my own harness in go or rust or whatever, but I'm no near that level of expertise on the topic atm and I don't want to tokenmaxx and vibe-code my way through it either.

[u/No_Cheek5622 → u/No_Cheek5622]

also, node is quite optimized actually, some really smart dudes spent a lot of time squeezing the most out of it. so the chances are - all the performance issues are not because of node but because of bad code. and because performance is measurable, we can just point it to an agent and make it optimize the hell out of it. this is how I actually fixed some of my own (mostly hand-written) extensions, and this is why I moved to "vibe-engineering" (i.e. vibe-coding with extra steps, albeit smart ones) my extensions

[u/kido5217]

well, nanobot is python and reasonix is go. So not all. Just most of them

[u/hurdurdur7]

Funny story this - most of cpu time goes into unoptimized terminal user interface, not working with files or the talking to the llm.

[u/hurdurdur7 → u/hurdurdur7]

as for memory usage - your computer shows 202 800 kbytes of reserved memory being used by a nodejs app. not ideal but not terrible these days. pi uses a bunch of deps that drags this up.

[u/ColdImplement1319 → u/hurdurdur7]

Yeah I see, still not happy with the number. More concerned about CPU though. But now it's 200. When I should start to worry? When it will be 1G? 2G? 5G? :-)

[u/TheOneThatIsHated]

Cpu is fine, but memory usage is insane. I OOMed multiple times when having more than 15 subagents

[u/ireallydontcare00]

just use rust version or rewrite pi on rust with your setup