Hacker News new | ask | show | jobs
by ChrisMarshallNY 22 days ago
Basically, my app is a memory hog. I went all-in on performance, and neglected frugality. Lots of caches, local copies, and pass-by-value.

I suspect the best solution will be architectural, which promises to be a pain.
1 comments
RobRivera 22 days ago
Yea, one cant go all in on performance, and then not co soder architecture.

A language choice is a starting point but you have to know the techniques of architecture learned.

link
ChrisMarshallNY 22 days ago
It looks like it wasn't too painful. I just kept a couple of array references too long. The LLM gave me some threaded crap, and I now need to make sure to let go, before another thread grabs the PC.

That's the issue with the new "memory is cheap" model. I cut my teeth with 256 BYTES (not KB or MB) of space for the program, the stack, and the scratch.

But I've gotten sloppy, over the years.

link