I have two wagn installations. one basing on 1.6.1 and one basing on 1.7.0. Both are running with mysql, apache and thin. Very often requests needs up to 1 minute until I see a page (quite ver very simple pages, e.g. http://wiki.kieznetz.de/). That is the same for start page, adding a card or sub pages. PHP based sites on the same server responses in that situations as fast as usual. Load on the server is not the problem. Each request results in a thin process that consumes up to 50% CPU load.
A strange thing is that:
[stop] /etc/thin/wagnKieznetz.yml ... Stopping server on 127.0.0.1:6100 ... Sending QUIT signal to process 7717 ... >> Exiting! Stopping server on 127.0.0.1:6101 ... Sending QUIT signal to process 7721 ... >> Exiting! Stopping server on 127.0.0.1:6102 ... Can't stop process, no PID found in tmp/pids/kieznetz-thin.6102.pid Stopping server on 127.0.0.1:6103 ... Can't stop process, no PID found in tmp/pids/kieznetz-thin.6103.pid Stopping server on 127.0.0.1:6104 ... Sending QUIT signal to process 7733 ... >> Exiting! There are always some thin processes that can not be stopped. But they were all started.
Is thin still a good choice? Together with redmine thin did a good job on the same server.
When I use actually WEBrick wagn responses mostly quite fast. But I have also seen long response times also with WEBrick.