Thanks Tim, Your suggestion makes sense. There was a demo. It's fast. The creator demonstrates it with an outdated Blackberry cell phone and it's 2 years ago. Everything should be greatly improved by now.
I hope you're right. On Tuesday, January 8, 2013 8:48:24 PM UTC+7, Tim Caswell wrote: > > Since you say it works fast locally and slow over internet, I'm guessing > the issue is bandwidth and internet latency. If the node proceess isn't > maxing out a cpu core, it's probably not the bottleneck. You may need to > change your architecture not your runtime. For example use node to set up > p2p connections directly between clients instead of proxying data through a > central server. > > Saying nginx is faster than node doesn't make sense. It's so much more > complicated than that. I've gotten several gigabits a second of data > through a single node process before, but depending on what your're doing, > it could be much slower. Are you proxying data through a pure js websocket > implementation? If so, that will eat a ton of cpu decoding the websocket > protocol thanks to the framing mask. > On Jan 8, 2013 2:35 AM, "Ket" <[email protected] <javascript:>> wrote: > >> Thank you for suggestion. >> >> Hope the details below would help. >> >> The hosting is A2Hosting, a vps package, based in Michigan. I know it's >> not powerful but I plan to upgrade over time. >> >> The node.js package is provided by Joyent on Github here: >> https://github.com/joyent/node >> >> The websocket package provides by Worlize on Github here: >> https://github.com/Worlize/WebSocket-Node >> >> And for the WebRTC script, I just simply turn HTML5Rocks.com upside down >> to sift out the codes. >> >> My initial intention is to use between friends and a small number of my >> clients and may expand if it works out so well. >> >> Thank you, >> >> On Tuesday, January 8, 2013 2:41:31 PM UTC+7, Marco Rogers wrote: >>> >>> From your link, it looks like you want to do live streaming to a dynamic >>> list of recipients. That is a large topic, and "use nodejs" doesn't begin >>> to cover it. Voxer does live audio streaming with node and they have a >>> large system and use many many servers. So I'd think real hard about >>> standing up something simple and expecting it to hold up in production. >>> >>> But you didn't ask that. You asked why it's slow on your web host. >>> You'll have to provide more information about what web host you're using, >>> your app architecture, and what "slow" means in order for someone to help >>> you out with that. >>> >>> Good luck >>> :Marco >>> >>> -- >> 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]<javascript:> >> To unsubscribe from this group, send email to >> [email protected] <javascript:> >> 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
