Is there an easy mechanism whereby a Neko application could check the amount of memory in use? Other than O/S-based mechanisms, would there be a way to see the memory usage from outside?
The first of those, if available, might be a good thing for the Neko app to log every (say) 5 minutes -- if it's consistently growing, something that might be fixable is wrong. J. Merrill From: Tom <[email protected]> To: Neko intermediate language mailing list <[email protected]> Date: 05/19/2010 01:31 PM Subject: Re: [Neko] Neko server stopping after a while (?) Sent by: <[email protected]> I've heard about issues with apache and using neko on a managed or shared server. For some reason the application would be terminated after a while on certain hosts. Could this be what caused the problems of the people I talked about earlier? 2010/5/19 Nicolas Cannasse <[email protected]> Tom a écrit : I'm sending this mail to both the Neko and haXe MLs as I think it concerns both. I'm interested in using Neko for a game server. To make sure that my decision is not going to disappoint me later on, I've asked around if people had any experiences with using Neko for a server which has to handle a lot of connections simultaneousely. Most reactions were good, although I heard from 2 people that their server application would sometimes simply quit, after a random amount of hours, without any warnings or error logs. This would of course be a big problem. I am wondering if anyone else has experience with this behaviour, and if it is related to Neko? One crash that might not be noticed by neko is a Garbage Collector one in case no more memory is available. Otherwise you should get proper errors on why the application is exiting, in case of uncaught exception for instance. Nicolas -- Neko : One VM to run them all (http://nekovm.org) -- Neko : One VM to run them all (http://nekovm.org)
-- Neko : One VM to run them all (http://nekovm.org)
