If you get bad performance with Sympa's web interface, below is a list of possible reasons :

FastCGI : not using the fastcgi Apache module leads wwsympa.fcgi process to start from scratch for every HTTP request. It is not reasonable to run Sympa web interface without fastcgi enabled in a production environment.

ServerName Directive. If the name of the machine running Sympa is not the exact hostname of the server, you should use this directive. Otherwise, performances decrease.

Sympa versions : we have introduced significant performance optimizations in Sympa 5.1, especially to allow better perfs on the web interface, with lots of lists

Using config.bin files : config.bin are binary versions of list config files. When used this web interface speeds up in a significant way. See cache_list_config parameter usage.

RAM on server : the CRU is running s ML service, hosting 800 lists on a FC4 server with 4Gb of RAM

Database : Sympa requires a RDBMS either mysql, Pg, oracle or Sybase. Mysql is the one used on the development platform and probably the only that provides the best performance.

Log level : setting a high log_level (sympa.conf parameter) will decrease performance. You should keep the log_level to 0 in a production environment (log_level 0 does not disable logs but just keep normal operation logs).

You should now perform whatever actions that you wish to profile on the Sympa web interface. You should perform the actions let's say 10 or 100 times to make the process init process negligible. Once you've simulated things on the web interface, you should put aside the generated tmon.out file : % cp /home/sympa/bin/tmon.out /tmp/

You then use the dprofpp tool to analyze the content of the tmon.out file :