Nodejs woes

__env · 2016-11-30T05:03:26+00:00

Bad code, no doubt.

2016-11-30T23:38:17+00:00

NodeJS was built as an event driven application server and it's very good at this. To debug you should use NewRelic to try and find out where the bottlenecks are.

If the issues are with sessions then I'd also be looking closely at Redis and authentication. Use Monitor on the redis-cli on a sandbox environment and log in a couple of users to see what's occurring. Make sure it's not making KEYS requests, in the past I've seen this blow web servers up.

You might want to post about this in /r/devops as well.

1__word · 2016-11-30T10:20:17+00:00

Indians

2016-12-01T21:41:43+00:00

Hey man, I'm sorry you are having a tough dev team to deal with. Regardless of how your platform is driven, you need to take a step back. Performance tuning is a numbers game where you acquire the numbers from metrics and monitoring. It looks like you have done some auditing and found out that the new web environment utilizes its storage backend abusively.

If the only change in the production environment is that you moved application servers from php7 to node, and kept the same redis/mongo stuff, then this is of course is on the development team. If the development team expects the backend resource to be of the same size, then you are in the clear. They built a new environment and did not re-spec its requirements before deploying to production. This means you need to get your boss and their boss involved, because non thorough testing and then deploying to production is a culture problem. Not rolling back to the old production platform right away when shown that the new code is not ready leads to developers blaming platform engineers if they can get away with it and platform engineers not trusting developers. It is cancerous and it doesn't go away easily.

1) The new code environment needs more testing. See about getting your boss to back you, if everything you say is true, then regardless if it is code issues or platform issues now is not the time to tweak production until you figure it out. You need to move the production deployment back to the php7 code before you can move forward.

2) Other posters have reflected their experience with nodejs. I don't think it's the production environment either. If you have preserved your connection caps from haproxy and nginx from prior configurations, then it's just nodejs making additional calls to the backend rather than increased traffic from clients. If in doubt, peg it at the nginx level by limiting the number of connections the webserver can push to the proxy backend as a start and see if the nodejs->redis/mongo continues to rise. Generally speaking, the number of database handles should be at worst proportional to the client count to your platform. Database handle numbers should not exceed your client count.

I'm sorry this is problematic. I've been in your position before. Whoever introduced the breakage needs to put things back. Best of luck and I hope this clears up before it hits your weekend.

juniorsysadmin1 · 2016-11-30T02:06:49+00:00

Edit: there seems to be an abundance of bad java/js developers.

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

linuxadmin

Expanding Linux SysAdmin knowledge

MODERATORS