3 ms·

A surprising Node.js failure: deterministic code becomes probabilistic under load

• bspates 10y ago
  Link to source broken.
  • lkrubner 10y ago
    What do you mean? If I click the headline I go to the article.
    • davidmurdoch 10y ago
      The article has a link to "source" at the bottom that 404s.
      • lkrubner 10y ago
        That article is the source, but yes, the source link should not be there.
• asusBsus 10y ago
  > it stores 4 gigs of data in memory I'm not sure how a single node process was able to load 4 gbs worth of data into memory? I thought there was a hard limit of 1.5GB per process.
  • davidmurdoch 10y ago
    It's 1.7GB (for 64bit node) unless you change the limit with the `--max-old-space-size` flag.
• euoia 10y ago
  Are you waiting for the data set to fully load before allowing the process to respond to requests? Are you running just a single node.js process or more than one? Does the node.js process restart if it crashes? Could you run in a debugger with a breakpoint inside a check for records being empty?