But : showing 6000 survey take more times than showing 10 :)

2-3 seconds : maybe need a static var for amll;groups

Related issue : https://bugs.limesurvey.org/view.php?id=18473

Can you activate debugsql and check number of requests ?

There are no surveys shown at all. The default survey groups has set 'List public' set to false.
Still it is so slow due to inheritance.

debugsql show (have 36 survey activated)

• 20 times User (have o nly one user) system.db.CDbCommand.query(SELECT * FROM lime_users t WHERE t.uid=1 LIMIT 1)
• 16 times X 9template : system.db.CDbCommand.query(SELECT template.id AS t1_c0, template.name AS t1_c1, template.folder AS t1_c2, template.title AS t1_c3, template.creation_date AS t1_c4, template.author AS t1_c5, template.author_email AS t1_c6, template.author_url AS t1_c7, template.copyright AS t1_c8, template.license AS t1_c9, template.version AS t1_c10, template.api_version AS t1_c11, template.view_folder AS t1_c12, template.files_folder AS t1_c13, template.description AS t1_c14, template.last_update AS t1_c15, template.owner_id AS t1_c16, template.extends AS t1_c17 FROM lime_templates template WHERE (template.name=:ypl0). Bound with :ypl0='bootswatch')
• 10 times Survey group (default) system.db.CDbCommand.query(SELECT t.gsid AS t0_c0, t.owner_id AS t0_c1, t.admin AS t0_c2, t.adminemail AS t0_c3, t.anonymized AS t0_c4, t.format AS t0_c5, t.savetimings AS t0_c6, t.template AS t0_c7, t.datestamp AS t0_c8, t.usecookie AS t0_c9, t.allowregister AS t0_c10, t.allowsave AS t0_c11, t.autonumber_start AS t0_c12, t.autoredirect AS t0_c13, t.allowprev AS t0_c14, t.printanswers AS t0_c15, t.ipaddr AS t0_c16, t.refurl AS t0_c17, t.showsurveypolicynotice AS t0_c18, t.publicstatistics AS t0_c19, t.publicgraphs AS t0_c20, t.listpublic AS t0_c21, t.htmlemail AS t0_c22, t.sendconfirmation AS t0_c23, t.tokenanswerspersistence AS t0_c24, t.assessments AS t0_c25, t.usecaptcha AS t0_c26, t.bounce_email AS t0_c27, t.attributedescriptions AS t0_c28, t.emailresponseto AS t0_c29, t.emailnotificationto AS t0_c30, t.tokenlength AS t0_c31, t.showxquestions AS t0_c32, t.showgroupinfo AS t0_c33, t.shownoanswer AS t0_c34, t.showqnumcode AS t0_c35, t.showwelcome AS t0_c36, t.showprogress AS t0_c37, t.questionindex AS t0_c38, t.navigationdelay AS t0_c39, t.nokeyboard AS t0_c40, t.alloweditaftercompletion AS t0_c41, t.ipanonymize AS t0_c42, SurveysGroups.gsid AS t1_c0, SurveysGroups.name AS t1_c1, SurveysGroups.title AS t1_c2, SurveysGroups.template AS t1_c3, SurveysGroups.description AS t1_c4, SurveysGroups.sortorder AS t1_c5, SurveysGroups.owner_id AS t1_c6, SurveysGroups.parent_id AS t1_c7, SurveysGroups.created AS t1_c8, SurveysGroups.modified AS t1_c9, SurveysGroups.created_by AS t1_c10, SurveysGroups.alwaysavailable AS t1_c11 FROM lime_surveys_groupsettings t LEFT OUTER JOIN lime_surveys_groups SurveysGroups ON (SurveysGroups.gsid=t.gsid) WHERE (t.gsid=1))
• 10 times system.db.CDbCommand.query(SELECT * FROM lime_surveys_groupsettings t WHERE t.gsid=0 LIMIT 1)

My opinion :
Need optimisation (static or better : caching) for template and SurveyGroups option

I totally agree.

When looking at the survey list page with only 1 survey listed I see 61 queries being run. Most of the repeated ones are for the template system. I think with some work the number of queries can be reduced by 30-50%.

This one : https://github.com/LimeSurvey/LimeSurvey/pull/3737
For SurveyGroupSettings : only DB call

For template : seems we don't( use (when need it) TemplateConfiguration::getInstanceFromTemplateName

For template : https://github.com/LimeSurvey/LimeSurvey/pull/3738

OK : SurveyGroup broken : i use the other for template

master : group settings : https://github.com/LimeSurvey/LimeSurvey/pull/3737

This one can be moved to cache for develop.
I think we only use model->save for SureyGroupSettings update ?
Maybe some saveAll ?

I start with instance with options (inherited from parent) … but need more rewrite.
Since survey update instance of SurveyGroup (WTF ?)

For 5X

https://github.com/LimeSurvey/LimeSurvey/pull/3738 has been merged in, but the number was wrong (18473), so it is not shown here.

@DenisChenu do we need this fix for 5.x as well?

do we need this fix for 5.x as well?

In my opinion : yes , same for the 2 others.

Here it's more : https://github.com/LimeSurvey/LimeSurvey/pull/3737 (SurveyGroups)

OK, confirm needed for 5.X too :)

I do the 3 for 5 (separate)

Ok, then please make a PR for 5.x when you get some time.

5.X : https://github.com/LimeSurvey/LimeSurvey/pull/3787