[Moin-user] CPU over 100% while "RecentChanges"

[Marcel Häfner]

Hi Thomas

Thanks for your answers, some feedbacks.

Am Montag, den 09.04.2007, 16:11 +0200 schrieb Thomas Waldmann:
> RecentChanges has quite some stuff to do. It is not just reading 
> edit-log and displaying it, it has to check existance and ACLs for every 
> page before showing (and it can't be cached because output can be 
> different all the time). lookup users, etc.. Thus, it is much more than 
> the static case.
ok I see the point. So if my site would get high load - it would be
definitely better to make a basic standart frontpage and not directly
link to the recent changes.

> 
> > c) Optimizing the Twisted Framework, how (maybe forking process; extend
> > the threads to 20 doesn't help a lot..)
> 
> FastCGI (and maybe even standalone?) has some better mechanisms for that.
I made now a second install with a standalone Moin and could now
delegate the Wiki's to the standalone or twisted instance (but still
using the same farmconfig). It's like a loadbalancing between multiple
CPUs :)

For me it looks like the Standalone Version is a bit faster, but the CPU
goes anyway up to 100% (and over). So, it is like you said about the RC;
It needs machine power and that's it!

In the Standalone Version there's also a "ForkingServer" available. How
I did read, it's still experimental and slow. 

--> Were the 1.6 and 2.0 Version of MoinMoin will heading? Is there a
Standalone Version obsolete?


> > d) Using Mod_Python or Standalone Modus (FastCGI ist not an option for
> > me)
> 
> Don't use mod_python. Why is fastcgi no option?
my provider just not supporting yet. 

--> But what's the Problem with Mod_Python? I did run some Intranet site
on a Windows/Apache and also Linux Fedora/Apache on an old P3/800mhz.
Both with Mod_Python. And without Problem well hope it stays this way,
don't fear me :-)


best regards
Marcel




====================================
Logfiles for a Standalone Wiki
====================================

1. RecentChanges
====================================
    * compile_huge_and_ugly = 0.000s
    * getACL = 0.002s
    * load_multi_cfg = 0.000s
    * run = 0.153s
    * send_page = 0.152s
    * send_page_content = 0.055s
    * total = 0.155s

2. Single Page
====================================
    * getACL = 0.002s
    * load_multi_cfg = 0.000s
    * run = 0.032s
    * send_page = 0.031s
    * send_page_content = 0.007s
    * total = 0.034s

3. Stress Test
====================================
[marcel at lestat ~]$ ab -n 100 -c 10 http://lotek.heavy.ch/Index
This is ApacheBench, Version 2.0.40-dev <$Revision: 1.146 $> apache-2.0
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Copyright 2006 The Apache Software Foundation, http://www.apache.org/

Benchmarking lotek.heavy.ch (be patient).....done
Server Software:        MoinMoin
Server Hostname:        lotek.heavy.ch
Server Port:            80

Document Path:          /Index
Document Length:        32752 bytes

Concurrency Level:      10
Time taken for tests:   12.660244 seconds
Complete requests:      100
Failed requests:        0
Write errors:           0
Total transferred:      3327003 bytes
HTML transferred:       3304884 bytes
Requests per second:    7.90 [#/sec] (mean)
Time per request:       1266.024 [ms] (mean)
Time per request:       126.602 [ms] (mean, across all concurrent
requests)
Transfer rate:          256.63 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:      142  176 299.4    145    3141
Processing:   660 1048 129.9   1062    1548
Waiting:      224  361 122.9    343    1106
Total:        811 1225 341.1   1213    4351

Percentage of the requests served within a certain time (ms)
  50%   1213
  66%   1257
  75%   1285
  80%   1295
  90%   1326
  95%   1368
  98%   1708
  99%   4351
 100%   4351 (longest request)