On Monday, November 19, 2012 7:52:43 PM UTC-8, Ket wrote: > > Base on my research (Googling), some people say that node.js consumes a > lot of memory. Is this true?
It can be. In my limited experience, that has a LOT more to do with how you code your application than node itself, however. You need to make sure that you're efficiently streaming the media (not reading too far ahead of what's been sent, etc). You might find more information searching here for "back pressure" as I know I've seen that term used in this context. Basically, if you just read in the file as fast as you can and send it, you could potentially wind up buffering most of the file on the output side, since disk IO is usually much faster than network IO once you're past the LAN (and sometimes even within the LAN, particularly if the file is cached in RAM). Even on a LAN, the client speed might prove to be a bottleneck rather than the LAN, though that's more likely the case with mobile devices rather than modern desktop machines. A few questions concerning the content: Is it static, or live streaming? Is it a single stream, or multiple? And how huge is huge? Any of these could affect any recommendations. -- 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
