3 ms·
Kei, I've just installed the node_sample "Hello World!" project on the free plan, and noticed it was running a bit slow. Apache bench shows an avg of 1471ms/req
by georgecalm 15y ago
Kei, I've just installed the node_sample "Hello World!" project on the free plan, and noticed it was running a bit slow. Apache bench shows an avg of 1471ms/req over 100 requests (from NJ). Do you provide faster response-times on the other plans? Where are the data-centers located?
- keikubo 15y agoWe are based on Amazon Web Services (ELB + EC2 + nginx + powerdns + apache + FastCGI). I admit the current response time is very slow, but our team members make a lot of effort to improve it. It may be the different issue, but some node hackers may disagree to use Node.js with Apache + FastCGI. However, it is our challenge to make the node technology available not only to geeks but also to light users who will take advantage of server side javascript. We'll improve the performance and I welcome any advices!
- jedberg 15y agoI would humbly suggest that you drop ELB in favor a software based solution that you control like haproxy. ELB just isn't up to the job unless you are a really big customer of Amazon's. Also, if you are using small or micro instances, you probably don't want to do that either. Don't use anything less than a large instance if you want even semi-decent performance.
- keikubo 15y agoThanks for your advice. I think chnaging load balancers to 64-bit instances is the first thing I should do. And also I heard several times about the performance of ELB, so we will change our architecture to some alternatives.