3 ms·

nice FUD headline

• andreyvit 15y ago
  Why? It's been a real bummer for me to find that out (the hard way).
  • irahul 15y ago
    Why? It's been a real bummer for me to find that out (the hard way). Knowing about the limit is hurting you, or you have really faced this constraint in a project? As mentioned elsewhere, node has buffers which are allocated outside of v8 heap, and the user data will largely be unaffected by the memory limit if you are using buffers.
    • andreyvit 15y ago
      I've tried to explain it in another comment: > To add my own perspective: I was running some analytics batch job on Node and hit this limit, had to add multi-stage processing to accommodate it. Using --max-old-space-size=1900 did help a bit. So yeah, it did affect me, although not on a typical web project. It wouldn't be a problem at all if I knew about this limit from the start. Thus this is a warning for others. (BTW another limit I was told about is that objects can't have more than a million keys. Thankfully I did not hit that one.)
      • peterhunt 15y ago
        Well, if your data set is big enough to hit that limit then you'll probably need to horizontally scale it out anyway... Or rewrite in C