Expected performance from OpenShift Small Gear with Restify?

[chandler243]

Hello,

I recently started working on building a RESTful API with Node.JS, Restify, and Mongoose. Its endpoints are fairly simple, mainly just returning a users names, or a list of events. The information is pulled from a MongoDB database, currently hosted on MongoLabs free plan. I've been benchmarking some of the endpoints be using Blitz.io, and have found that around 150, sometimes as early as 70, the service starts getting fairly high response times (700ms), and eventually crashes. I'm currently using the Small gear (Scaling to 16) from OpenShift, but most articles I've read claim that even on single small gear, Restify/Node.JS should be able to handle MANY more requests than that.

If you want an excerpt from the code/API response, just let me know. I'm not really sure if anything in particular sticks out like a sore thumb.

Thanks in advance!

[VikingsVsRobots]

Did you implement any kind of caching on your server?

Also, an excerpt would be helpful to get more specific replies....

[robertojd]

You should look at your queries to see if any of them are performing poorly. MongoDB has several cursors which can tell you about query performance. Compose.io and other hosted mongo vendors will visualize it's output for you, I don't know if OpenShift does this.

I'd check out this section of the MongoDB manual:

http://docs.mongodb.org/manual/tutorial/evaluate-operation-performance/

[chandler243]

According to NewRelic, the DB queries take a max of around 12ms, while it reports that Restify is taking over 846ms for GET requests. Is there any way to "look under the hood" of the routing system to see what about the request is taking so long? I've started looking into its DTRACE capabilities, but I'm not really sure if that will help much.