This depends largely on load. If you're talking about an application with a single or very small number of users, then determining raw speed will determine server vs client. However, if you have multiple concurrent requests then it will usually be faster to push the work to the client as each client can do the work for themselves instead of having the server to the work for all clients.
That said, raw performance is rarely the most important concern. Certain tasks simply lend themselves better to be done on server vs client and other considerations like bandwidth usually override those decisions. In addition there are other options than just server/client like creating a pool of server processes or pool of servers to perform certain processing if the task is appropriately handled on the server and load is high. hth, Sam On Friday, July 12, 2013 4:45:27 AM UTC-4, Ket wrote: > > I've an identical processing javascript function that run on both node.js > server and a browser (chrome). I've no idea how to test which side is > faster. > > Does it's the right idea to run it on a server and render on chrome, or > should I process on chrome alone. > > In this case, does node.js act as native app. My priority concern is > performance (faster). > > Thank you, > -- -- 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 nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
