The box is running Node.js 0.6.1

The node process is a webserver running a web application. I'm not
using express, it's simple enough that I hand rolled the application.
It is also not doing websockets or long polling, or anything fancy. It
is making HTTP requests to an outside CouchDB service, HTTP calls to
the SendGrid email API, and rendering HTML templates, compiling Less
CSS, and compiling CommonJS modules for the browser.

However, my philosophy is to deploy the app without any optimizations
at first (for low traffic sites like this). So, every single request
requires recompiling and rendering Swig templates, recompiling Less
CSS, and recompiling the CommonJS modules depending on the mime type.
I'm not caching CouchDB results either. However, despite all this lack
of a caching layer, the most expensive page views only tax the
processor at less than 20%, until it starts to trend upward again over
a period of several weeks. I plan to turn on my caching mechanisms
soon, but would like to figure out why this is more processing power
over time.

If this does not happen again, I'm going to assume the incident over
the past couple of weeks was the fault of AWS and not Node.js. It just
seems so strange that the Node.js process became so expensive for the
same requests as time went on over a period of weeks. I'm thinking
maybe Swig or Less may be to blame. Just not sure where to look yet.

On Feb 16, 3:56 pm, mscdex <[email protected]> wrote:
> On Feb 16, 2:40 pm, Kris Walker <[email protected]> wrote:
> What node version are you using and what is your node process doing
> exactly? It's hard to tell without more details.

-- 
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 [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

Reply via email to