Tags:
create new tag
, view all tags

Question

Our Twiki installation is running too slow for the last few days. Server(4 CPU 4 GB RAM)

When we do top and ps -aux we find that oops and search processes are eating up a lot of CPU cycles.

Yesterday we deployed twiki again on another machine with the same content.(copied data and pub dirs). On this machine(1 CPU 1 GB RAM) the performance was real good.

Can somebody tell why these oops and search processes keep on running?

Attached are the results for top and ps -aux commands

Environment

TWiki version: TWikiRelease04x00x02
TWiki plugins: DefaultPlugin, EmptyPlugin, InterwikiPlugin
Server OS: Suse Linux
Web server: Apache 2
Perl version: Perl 5.x
Client OS:  
Web Browser: IE, Firefox
Categories: Performance

-- GurvinderSidhu - 16 Jun 2006

Answer

Well, I guess TWiki just looooves well dimensioned hardware smile

I have reported this as a bug in our bugtracker, open as Bugs:Item2494.

We will probably need to debug this a bit further, so if you have a possibility to install an apache module that will tell you a bit more about the processes (report full urls etc) I'm sure this will be helpful in troubleshooting this.

-- SteffenPoulsen - 16 Jun 2006

after waffeling on a little about differences between the machines, i had an actually useful thought - is your /tmp filling up with session files? or your apache or twiki log files getting big?

we've had similar sorts of issues when we forgot to use log_rotate on the apache logs...

-- SvenDowideit - 16 Jun 2006

 
Topic attachments
I Attachment Action Size Date Who Comment
Texttxt TopAndPsauxresults.txt manage 7.3 K 2006-06-16 - 11:32 GurvinderSidhu Results of top and ps -aux commands
Topic revision: r3 - 2006-06-16 - SvenDowideit
 
Twitter Delicious Facebook Digg Google Bookmarks E-mail LinkedIn Reddit StumbleUpon    
  • Download TWiki
TWiki logo Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2012 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.