performance problem

[derMicha]

Hi,

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.

What ist the best setup for wagn? 

Cheers,

Michael

--
Michael Merz
Mail: derm...@dermicha.de
Skype: michamerz

[Ethan McCutchen]

Hi Michael,

I will respond to specifics in a separate email to the wagn-dev group because we try to keep most of the low-level tech stuff out of this list, but I did want to send a few highish-level comments to this list:

1. Our hosted wagns have been having some performance problems over the last few days.  I apologize to anyone that's been inconvenienced.
2. The good news is that I deployed a few fixes and optimizations today that should speed things up considerably and help avoid bogging.  Please do let me know if you have problems.
3. Wagn is highly dependent upon "caching" info to avoid extra database lookups.  If you have a local wagn and it is extremely slow, it's good to start by looking into caching.

... more detail coming to the wagn-dev list.

- Ethan

--
You received this message because you are subscribed to the Google Groups "Wagneers" group.
To post to this group, send email to wagn...@googlegroups.com.
To unsubscribe from this group, send email to wagneers+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/wagneers?hl=en.

--
Ethan McCutchen

One of the Wagneers, Wagn.org

Wagn. How pioneers roll.

s: ethan.mccutchen

t: @intogreater