As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Locked. This question and its answers are locked because the question is off-topic but has historical significance. It is not currently accepting new answers or interactions.
I'm new to Node.JS, already Googled for aswers but there is a lot of ways of doing this.
Do you have some sort of math to know when I'll need to scale my Node.JS server? And what tools you use for monitoring server performance and error track?
Thanks!
As #ThiefMaster said, this depends on your system. You need to monitor the requests for your site, the CPU load, memory footprint etc and decide if and when to add mode servers.
If you want to know more about Node.js performance read this good article: http://blog.3rd-eden.com/post/5809079469/theoretical-node-js-real-time-performance
If you need a Node.js metrics library, there are 2 ones which I can recommend: https://github.com/felixge/node-measured
https://github.com/mikejihbe/metrics
Resources:
monitoring a node.js server
I recommend monitoring your event loop and if it starts to back up more than 200ms on a regular basis, you'll need to scale.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I create a web server with Node.js. I'm using the Express framework. The database is MongoDB.
I want to host web server on a Linux machine. I don't know how to make the decision between the different Linux distributions, such as Debian, Unbuntu or RedHat.
My questions are:
What is the main difference of the different distributions?
Which factors should I take into account?
Which one is better for my requirement?
What is the main difference of the different distributions?
Nothing. (As long as running node.js is the only concern)
Which factors should I take into account?
Whether any unresolved issues are yet to be addressed by node.js.
Which one is better for my requirement?
I would consider Ubuntu, as it's popular & bugs are addressed faster due to shorter release cycle.
I'm using it in Debian. Rock solid!
In your case it also complies with the clever tip that Joachim Isaksson gave you - use whatever you're familiar with.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am developing a ASP.NET MVC app deployed on Azure, and looking for a library providing asynchronous transport mechanism/fallback.
After my own research, I've concluded that there are two well-known candidates - Socket.io and SignalR.
My question is simple) What's the pros and cons of them? It there any good reason to use one over the other?
thanks :)
I'd have to say that SignalR is definitely the best approach for your application. With the current build our laptops serving as servers are pushing around 350k messages/s. With the next release it will be even higher (several multiples higher judging by current tests).
Check out the main site: http://signalr.net/
The GitHub: https://github.com/SignalR/SignalR
JabbR for questions: http://jabbr.net/#/rooms/signalr
I've never used SignalR and according to what google tells me it is a replacement solution for .Net apps.
So I guess you should give it a try.
Socket.IO is awesome, I love it but I'm a noder. According to their doc there is no .net/c# bindings. Maybe their doc is not up to date.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I have a production web service built with Node JS(HTTP Server) on a Linux box with a HAProxy Load Balancer and wanted some kind of graphical tool to do live reporting on the server. I specially wanted to look at requests/min, request failures, etc. Anything out there people would suggest. I need something non-intrusive b/c I will be handling 20mil+ requests a day.
Have you looked at cube (https://github.com/square/cube), graphite/carbon (http://graphite.wikidot.com/) or opentsdb for such data monitoring/display?
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
Well of course we could use quartz.net, which comes with nice features like concurrency control and load balancing. However it seems a bit bloated to me.
1) Am I wrong about this ?
2) If not how would you implement a cloud compliant scheduler (ie: either deployed on premise or within azure) ? Is Lokad scheduling the best approach ?
Based on the answers to this question ( Recommend a C# Task Scheduling Library ) quartz.net running in a worker role instance is the way to go.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am looking for a way to get some sort of monitoring, statistic or management data out of a node.js server instance - not sure what to search for or where to start. Any advice appreciated.
Stats would be requests processed (if applicable) - number of connections and so on.
Don't know if it will fit your needs, but you can try to look at node-monitor. Also Joyent is doing some advanced real-time performance analysis stuff, but it's probably only for their cloud services.
Nodetime can monitor different metrics, such as HTTP Response time, CPU time, OS Load, etc. It is also possible to set up email Alerts based on these metrics. More in the blog post Monitoring Node.js Application Performance.