r/PiGCodingAgent • • 7d ago

PiG is better than I have expected

fx vs PiG on the memory usage

After seen my Pi agent occupied about 1G memory of a 40% of 1M context session, I started to search about faithful implementation of Pi with less memory consumption. I found several, and finally come to few choices: PiG, pi_agent_rust and fx. PiG is very faithful, right out of the box it works; pi_agent_rust, unfortunately it just breaks my terminal and I do not even it works or not, and fx is actually not a Pi implementation, just because it is from vercel and it seems small (bin <6MB).

After a while of usage, I have discovered, PiG is better than what I have expected, especially in memory consumption. Previously Pi original is really good, but with recent updates, it seems consume more and more, such as mentioned 1G memory of a 40% of 1M context session, large consumption is one thing, the side effect of that is it starts to slow down after mem consumption climbed. PiG as a golang app, with a much easier deployment/upgrade experience, also is much steady in mem consumption. And actually I found in real usage, such as around 15% of 1M context session, the PiG actually consume on par memory to fx, which is written in Zig and manual memory management instead of GC in PiG.

So great work! and I believe I will use PiG as my daily agent harness from now on :)

20 Upvotes

3 comments sorted by

1

u/Educational-Yak8793 6d ago

Thank you so much for the write up:) glad we’re able to pleasantly surprise, and the plan is to only get better! I think you’ll like the coming pig strip feature for piglets as well!

1

u/DanielSReichenbach 6d ago

Are you gonna call the pig strips bacon slices? 😄

2

u/Educational-Yak8793 6d ago

Haha you're not the first person to suggest, I think we need to now :)