3 ms·
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 s
by ChrisMarshallNY 5mo 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.
- RobRivera 5mo agoYea, 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.
- ChrisMarshallNY 5mo agoIt 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.