Changes between Version 1 and Version 2 of Ticket #11649, comment 28
- Timestamp:
- Jan 9, 2014 11:36:32 AM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #11649, comment 28
v1 v2 5 5 However, that was solvable by replacing {{{ #!/bin/sh }}} with {{{ #!/bin/bash }}} 6 6 7 But unfortunately the script didn't crash the vm. I think this could be related to nodejs' non blocking I/O architecture. What happens (at least I think this is what happens) is that npm asks very fast for multiple DNS entries and queueing the answer in a callback. So we get multiple simoultaneously DNS requests although the answer hasn't arrived yet. 7 But unfortunately the script didn't crash the vm. 8 9 I think this issue could be related to nodejs' non blocking I/O architecture. What happens (at least I think this is what happens) is that npm asks very fast for multiple DNS entries and queueing the answer in a callback. So we get multiple simoultaneously DNS requests although the answer hasn't arrived yet. 8 10 What the script does is (if I read that correctly) opening sequently 100 dns queries and *waiting* for the reply before opening another. 9 11 Could this be right? … … 12 14 13 15 I have no background with nodejs whatsoever, but I'll ask a friend of mine to write a nodejs script that opens many simoultaneously connections to one server and maybe that script will crash the VM as well. 16 17 Please also note that I have a very fast internet link (100mbit) with a very low ping (usually < 10ms) and a direct connection (lan) to the router, so that might favor this issue. My MacBook is connected through WLAN, maybe that's one of the reasons why this doesn't happen there.
