Hacker News new | ask | show | jobs
by bootloop 2311 days ago
I would imagine it might make sense if you offload some short, less frequent but memory intensive sub-routines (sensors, navigation) to run in parallel to the rest of the system. But I would still avoid having a system wide dynamic memory management and just implement one specifically for that part.
2 comments

Whichever ones you allow to run in parallel need to have enough memory to run at the same time, but such a situation might happen quite rarely.

In other words, that sounds like a system where dynamic memory management is significantly riskier and harder to test than usual!

Why not static allocation, but sharing memory between the greedy chunks of code that can't run parallel to each other? (I assume these chunks exist, because otherwise your worst-case analysis for dynamic memory would be exactly the same as for static, and it wouldn't save you anything.)

> Why not static allocation, but sharing memory between the greedy chunks of code that can't run parallel to each other?

That's what I wanted to say with my comment actually.

when you design the system, you make sure there is enough physical RAM to do the job. Period. the problem space is bounded.