Let's see if I can help. I'm not experienced enough with node but I've been working on other platforms long enough to tell you that, as it has been said before, if is not the fastest it's close enough.
node.js has little to do with the network speed of your web server. The hardware on a web server has little to do with the network speed. There are more than enough examples of things that node.js asides from powering "text chat". You could process php files and use node.js to give the client the results. You could process node.js and use apache to give the client the processed files. (not the best idea...) You could run a program that has nothing to do with serving files or providing a service to a remote app with node.js . All I can say is you're either doing it wrong or you might have actually found a bug. If you know what you're doing, you will know that your messages are not being very helpful (for the people tying to help you or for you) as you failed to provide any of the following: - A description of what you're doing or trying to do. - A code sample of what you're doing (does not have to be the whole app) - A description of your local network's server - A description of your production/staging server - A description of the network's bandwidth of either of the servers On a different note, I'm working on a linux box with 1GB or ram, 120GB HDD and an AMD Athlon(tm) 64 Processor 3000+, 1 cores and that's why I'm noticing a real difference with node.js Big hardware == Little difference Little hardware == Big difference Regards, Juan S. Simon On Sun, Dec 9, 2012 at 4:05 AM, Ket <[email protected]> wrote: > I've a proof. I'm trying my project. I can't show anyone right now. If I > show you you'd beat me to it. I've tested with my friends who know nothing > about computer programing. They like my project but the speed. I have no > doubt about node speed. It's fast on local network, but not the web. > > Show me if you see any web project beyond text chat that powered by > node.js. > > Thanks > > > On Sunday, December 9, 2012 12:49:04 PM UTC+7, Arunoda Susiripala wrote: > >> I really cannot get exactly what you are saying. >> It seems like you are doing something terribly wrong. >> >> NodeJS is not the fastest. But it is fast enough with the other goodies >> if provides. >> Node does not take much resources and it run on any common hardware. >> >> Please tell us what you trying to do. any sample code, then we can help >> you out. >> >> On Sun, Dec 9, 2012 at 10:50 AM, Ket <[email protected]> wrote: >> >>> nodejs >> >> >> >> >> -- >> Arunoda Susiripala >> >> @arunoda <http://twitter.com/arunoda> >> <http://gplus.to/arunoda>https://github.com/arunoda >> http://www.linkedin.com/in/**arunoda <http://www.linkedin.com/in/arunoda> >> >> -- > 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 > -- 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
