-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
我在 worker.js 里 console.log('ooxx'),在浏览器刷新页面会出现2~5条的ooxx,什么情况? #27
Comments
我用的是Express, |
代码弄上来给我看看 |
就你wiki上的代码 |
就在 |
具体代码得4号上班才能贴上来了 |
另,如果一服务器有多个独立app, |
肯定是随项目走了 |
你console.log的意思是每个HTTP请求进来都打印一个ooxx |
master.js: var master = require('pm').createMaster({
pidfile: __dirname + '/tmp/jenny.pid'
})
master.register('http', __dirname + '/app.js', {
listen: 3000
})
master.on('giveup', function(name, num, pause) {
console.log('Master giveup to restart "%s" process after %d times. pm will try after %d ms.', name, fatals, pause)
})
master.dispatch() app.js: var express = require('express')
var mongoskin = require('mongoskin')
var app = express()
app.configure(function() {
var db = mongoskin.db('xxxx', { safe: true })
app.use(function(req, res, next) {
req.db = db
next()
})
})
var http = require('http').createServer(app)
require('pm').createWorker().ready(function(socket, port) {
http.emit('connection', socket)
console.log(
'Express server listening on port %d within %s environment.',
port, app.get('env')
)
})
然后在浏览器访问 |
这个没错的,每个request打印一个console.log。 |
app.js 调整下: var express = require('express')
var mongoskin = require('mongoskin')
var app = express()
app.configure(function() {
var db = mongoskin.db('xxxx', { safe: true })
console.log('MongoDB connected')
app.use(function(req, res, next) {
req.db = db
next()
})
})
var http = require('http').createServer(app)
require('pm').createWorker().ready(function(socket, port) {
http.emit('connection', socket)
})
console.log(
'Express server listening on port %d within %s environment.',
3000, app.get('env')
)
|
你是8核CPU么?默认按CPU数起进程的 |
4核的啊 |
No description provided.
The text was updated successfully, but these errors were encountered: