top | item 14000299

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

12 points| lkrubner | 9 years ago |smashcompany.com | reply

7 comments

order
[+] euoia|9 years ago|reply
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?

[+] asusBsus|9 years ago|reply
> 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|9 years ago|reply
It's 1.7GB (for 64bit node) unless you change the limit with the `--max-old-space-size` flag.
[+] bspates|9 years ago|reply
Link to source broken.
[+] lkrubner|9 years ago|reply
What do you mean? If I click the headline I go to the article.