TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Node.js performance tips from Linkedin

13 pointsby gwsover 13 years ago

2 comments

ntkachovover 13 years ago
I'm a little confused about this article. Its a little all over the place and not very helpful. First of all #10 has nothing to do with node at all and is quite obvious for anyone dealing with mobile web.<p>Second of all, some things not mentioned, don't use node.js to gzip stuff. Put nginx as a proxy and make THAT gzip stuff that node sends through. You really don't want node doing expensive operations like that on each request. nginx will do it faster and avoid blocking.<p>Rendering server side is fine if done right and you're not using a CDN. Storing all parts of a template in an array and using Array.join() is fast, clean and will reduce a lot of overhead vs. having two separate requests from the same client for a single webpage. But node isn't really made for templating where RoR/Django is so pick your tech stack better if you need templating.<p>This article boils down to user node as a JSON relay. Which in all honesty is probably the best thing to use node for. Have node format json data and send that around.
评论 #3468558 未加载
porsover 13 years ago
#6 Go Parallel<p>Uhm yes, that's the whole idea of using node isn't it? Handle each job that takes a bit of time asynchronously. Pretty obvious.