Interesting. The question is why have they been sat there for that long and what have they been doing? Unfortunately, we've rather 'inherited' this application so we can't really tell.
I'm wondering whether global queuing is hindering rather than helping here but it is the only way I can see whether things are really being held up. This is what I've got now after a restart and things ahve calmed down. We've got two processes that have done the bulk of the work:
----------- General information -----------
max = 14
count = 14
active = 13
inactive = 1
Waiting on global queue: 0
----------- Domains -----------
/var/www/rails/ccesd/site/current:
PID: 22775 Sessions: 0 Processed: 1289 Uptime: 2h 38m 7s
PID: 22777 Sessions: 1 Processed: 0 Uptime: 2h 38m 6s
PID: 22781 Sessions: 1 Processed: 0 Uptime: 2h 37m 44s
PID: 22787 Sessions: 1 Processed: 0 Uptime: 2h 37m 14s
PID: 22791 Sessions: 1 Processed: 0 Uptime: 2h 37m 5s
PID: 22793 Sessions: 1 Processed: 0 Uptime: 2h 37m 3s
PID: 22773 Sessions: 1 Processed: 1 Uptime: 2h 38m 17s
PID: 22785 Sessions: 1 Processed: 1 Uptime: 2h 37m 44s
PID: 22783 Sessions: 1 Processed: 2 Uptime: 2h 37m 44s
PID: 22755 Sessions: 1 Processed: 21 Uptime: 2h 44m 27s
PID: 22759 Sessions: 1 Processed: 14 Uptime: 2h 40m 36s
PID: 22757 Sessions: 1 Processed: 52 Uptime: 2h 43m 28s
PID: 22975 Sessions: 1 Processed: 0 Uptime: 1h 10m 25s
PID: 22779 Sessions: 1 Processed: 1299 Uptime: 2h 37m 55s
Would increasing pool size really help, which is what I've read when global queue is not showing zero?