Skip to Content.
Sympa Menu

en - Re: [sympa-users] crazy slow web interface

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: David Verdin <address@concealed>
  • To: address@concealed
  • Subject: Re: [sympa-users] crazy slow web interface
  • Date: Thu, 04 Mar 2010 11:28:04 +0100

The debug mode is used to log anything Sympa does. That means a lot of logs, that's why it slows down the web interface. Something you can do to have more logs without switching to the full debug mode is using the web interface too increase the log level. You can do so by going to the main server admin page and click the "Logs" tab.
However we think Sympa logs too much, whatever log level is used. That's something we plan to improve. We need first to improve the definition of each log level, to help admins to understand what log level they need.

Regards,

David

Le 29/01/2010 20:23, Christian Dahlhausen a écrit : What I also discovered is that turning on debug logging on Sympa, slows down the web interface significantly.  Browsing through the menus takes up to 10s per click.


On Mon, Jan 11, 2010 at 7:10 PM, <address@concealed> wrote:
I'm new to sympa, setting up 5.3.4 on a debian lenny machine.  I've got
apache, fastcgi
and suexec configured and working.  My db is postgres, on a separate
machine.  I've
also set up expl/ and wwsarchive/ dirs on an NFS share.  I've configured
sympa to use
nfs locks.  I've got only one user, me, and two test lists.

The web interface is sluggish, and when I click to administer a list, it
gets crazy slow.
Each page takes about 35 seconds to load.  When I turn on debugging, I watch
it acquire
and release locks, over and over again.  I counted 33 per request.  I also
see it gettext'ing
the same text over and over.  Sometimes a lock fails, wwsympa dies and
fastcgi restarts
it.  This happens every 5-10 requests.

I read over the performance page, and did some profiling.  I can post that
if it'd be
helpful.

Hopefully I should be seeing better performance.  If so, any suggestions for
what I might
be doing wrong?  Anyone using NFS shares out there?

Also, wwsympa.fcgi catches TERM signals, so the fastcgi process manager
can't kill them.
I verified this by sending them TERM by hand.  USR1 works, but TERM does
not.
Is this a known issue?

John



--
-----------------------------------------------------------
Christian Dahlhausen, Network Systems Engineer
University of Virginia - ITC Network Systems
PO Box 400324, 2015 Ivy Road, Charlottesville, VA 22904


-- 
David Verdin
Comité réseau des universités



Archive powered by MHonArc 2.6.19+.

Top of Page