On Mar 16, 4:46 pm, Jimb Esser <[email protected]> wrote: > The server in question is not an http server, but a back-end > simulation server running physics simulation for an online game using > a Bullet native library. Yeah, I know, not exactly a typical (or > perhaps wise...) use of node.js. We're 95% certain the Bullet module > is the culprit, but that is hundreds of thousands of lines of 3rd > party C++ code, not something feasible to poke in, and, like most > physics simulations, not particularly deterministic when combined with > the randomness of network latency and real user actions. Stand alone > stress tests we've tried never exhibit the problem, and since it takes > a fully loaded server a day to exhibit it, it's not likely to > reproduce in a development environment. That being said, it > consistently does reproduce on the production servers, so that is, > theoretically, an easy way to debug it with post-mortem debugging > (albeit with a day-long turn-around to test fixes). Heap dumps are a > much more reliable way of tracking down heap issues in a large system > than any "poke at different parts of the system at random" method, I > was just hoping there was an easy way to get them reliably...
FWIW I wonder if either of these javascript bullet ports are worth trying/looking into?: https://github.com/adambom/bullet.js/ and https://github.com/kripken/ammo.js/ -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
