The mailing list for listmasters using Sympa

[Kazim Koybasi <address@concealed>]

Hello,

Thanks for supplied information. We anayzed all queries with general log option in MYSQL. Then we created mysql index with most common queries and decreased index load times to down to 6 sec.

Best Regards.

On Wed, 16 Oct 2019 at 17:35, McLaren, Terry <address@concealed> wrote:

Kazim - Attached is a summary of the settings that optimize mysql for sympa.

 

Hope it helps,

 

Terry McLaren

University of Illinois

 

From: address@concealed <address@concealed> On Behalf Of Steve Shipway
Sent: Tuesday, October 15, 2019 3:01 PM
To: Kazim Koybasi <address@concealed>
Cc: address@concealed
Subject: Re: [sympa-users] Slowness at sympa web interface

 

On Mon, 2019-10-14 at 22:04 +0300, Kazim Koybasi wrote:

Thanks for informations. I set slow query parameters in mysql to detect slow queries but nothing is written in log. Our database not contain all information so I doubt that the reason is slow queries. . Can you explain that how we can create index in database about sympa list names?  I do not understand meaning of index creation in database . We also have external database resources which feeds our list content. I suspect from them. Do you have any other advise for solution.

 

If the web interface is responding slowly due to slow queries on the database, then you can sometimes add an additional index that will help speed up the query.  Occasionally, an index is missing and as a result the database needs to scan all items rather than use an index to quickly identify the ones wanted.  If this is the case, then your database Slow Query log should be able to point out the queries taking time.  Which index to create and how to tune your database depends on your situation; check with your DBA.

 

Another possibility is that you have your external datasources TTL set incorrectly.  If you have the ttl and distribution_ttl  settings too low (ttl defaults to default_ttl) then this can cause the external datasource to be polled to refresh the membership when you try to access the list.  If the datasource is extremely slow to respond this can slow things down. These should be fairly high - 1 hour is normal, but I used 1 day for some lists with membership that rarely changes.   If the list is low-activity, then maybe set ttl to a day or more and have distribution_ttl to something lower, like an hours or less.  You might also consider having a periodic job to automatically refresh these overnight.  Finally, you can set a time limit on external queries if you want; you might like to do this to limit the time taken by external queries.

 

Steve

 

 

 

--
Steve Shipway | Senior Email Systems Administrator 
Phone: +64 9 302 0515 Fax: +64 9 302 0518 
Freephone: 0800 SMX SMX (769 769) 
SMX Limited: Level 10, 19 Victoria Street West, Auckland, New Zealand 
Web: http://smxemail.com 

This email has been filtered by SMX. For more information visit smxemail.com.