tdebarochez/connect-couchdb — Issue #13: cpu and io load
Author: Jimflip
Created: 2012-01-14 22:42:46+00:00
State: open

Been trying this out on a VPS with a simple app with very low traffic (still in test).

I noticed when using this for session store my cpu usage jumps up 5% (5 minute average) and was then climbing at an approx rate of 2% per week.

Similar with my IO rate, jumped to 50 blocks/sec and then climbed at a rate of approx 50 blocks average per week (i.e. after running for a week my IO rate had increased by an average of 100 blocks per second).

I've gone back to using a memorystore and my IO rate and CPU usage has dropped back down to before I used this middleware.

My app is using couchdb elsewhere (seperate DB from session and using cradle).

While I can understand an increase in load due to periodic updating/cleaning, I think there must be a problem somewhere causing the load to increase at such a steady rate.

I tried investigating what could be causing the increase in IO and iotop pointed the finger at kjournald.

Also I'm not actually using the session to store anything yet!

Running on Lindode VPS 512 (just running, a single instance of this node.js app with couchdb).
Ubuntu Server 10.10 with node@0.6.2

├─┬ connect-couchdb@0.2.2
│ ├─┬ connect@1.8.5
│ │ ├── formidable@1.0.8
│ │ ├── mime@1.2.4
│ │ └── qs@0.4.0
│ └── request@2.9.3
├─┬ cradle@0.5.7
│ ├── vargs@0.1.0
│ └─┬ vows@0.6.1
│ └── eyes@0.1.7
├─┬ express@2.5.3
│ ├─┬ connect@1.8.5
│ │ └── formidable@1.0.8
│ ├── mime@1.2.4
│ ├── mkdirp@0.0.7
│ └── qs@0.4.0
├─┬ handlebars@1.0.2beta
│ ├─┬ optimist@0.2.8
│ │ └── wordwrap@0.0.2
│ └── uglify-js@1.0.7
├─┬ jade@0.20.0
│ ├── commander@0.2.1
│ └── mkdirp@0.2.1
└─┬ nodemailer@0.2.4
└── mimelib-noiconv@0.1.5

If I can help debug/test then just shout.