3 ms·

In reality, if you know your requirements up front, you do not need to dynamically allocated memory

• kstrauser 2y ago
  My requirement is to store and process arbitrary uploaded data. How’s that work out?
  • FactKnower69 2y ago
    [flagged]
    • kstrauser 2y ago
      You know a lot of device drivers that store and process arbitrary data?
    • dang 2y ago
      We've banned this account for repeatedly posting unsubstantive and flamebait comments and ignoring our request to stop. https://news.ycombinator.com/item?id=42347380 https://news.ycombinator.com/item?id=42347380 https://news.ycombinator.com/item?id=42353622 https://news.ycombinator.com/item?id=42353622 https://news.ycombinator.com/item?id=42372172 https://news.ycombinator.com/item?id=42372172 https://news.ycombinator.com/item?id=42374785 https://news.ycombinator.com/item?id=42374785 If you don't want to be banned, you're welcome to email hn@ycombinator.com and give us reason to believe that you'll follow the rules in the future. They're here: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html.
  • yjftsjthsd-h 2y ago
    Couldn't that work? Upload by chunks via static buffer (which I kinda thought is how most web servers actually do uploads?), save to a file, then likewise load+process+store in 1k chunks or whatever. Depending on what processing you're doing and the workload characteristics (most obviously, number of clients) it might be painful, but I think it could work fine with a fixed memory footprint?