the question index when present on a survey really slows limesurvey down.

This get worse (page loads of 5-10 seconds, 0-1 without the index) dependingon how many groups/pages are displayed on the index.

Does limesurvey recalculate the index everytime someone clicks on next?

I tested the same survey without the question index and the performance was normal, less then 1 second response time to load the next or previous page.

so the question index really is slowing things down on large surveys

Hello,

Maybe you can leave a export of the survey, then we can have a look.

And:

This will be fixed in 2.0. In 1.92, it LS does rebuild the index every page, and requires at least one database query per group (and possibly a db query for every question in every group if there are many conditions), before the current question. In 2.0, there is only a single database query per page regardless of survey length.

Question is if it is just the DB query causing the problem. Somehow the index seems to be the culprit. Did you test in question by question mode?

Mazi-

It's a combination of problems - basically the index needs to first check conditions to see whether the index element (whether question or group) should be displayed, and then check the session variables to see whether any questions within that index item were unanswered (so it can color-code it red). I'm nearly done moving all that functionality to Expression Manager, which will replace the way the index is built and managed.

Shnoulle wrote:
unfortunatly I cannot leave a copy of that survey for various reasons

TMSWhite wrote:
I can understand why the index needs to be rebuild if you skip several groups to a later page, but I cannot understand why it needs to check again when it goes just 1 page up, it should only check the new page and all the rest will stay the same right?

When you say Expression Manager you mean LS 2.0?

Eddie, the index is checked each time because there might be chained conditions and the like. All this can get very complex. As for now I can only recommend to disable the index if it loads too slow. Maybe you can also test on our online demo if this is reproducable there:

demo.limesurvey.org/admin
Username: admin
Password: test

As for the bug report: I doubt that anybody will touch this because of the complexity and the fact that the Expression Manager at the upcoming Limesurvey 2.0 will probably deal with it.

Yeah I understand, unfortunatly this survey without an index is unaccepable. And also it has to run normally

So I have a problem I think, gonna give the machine alot more CPU power and make it dedicated for just 1 survey and see what it does.

Then dive into the code myself to see if I can make some adjustments that will help the speed.

I also understand that no-one at the community would touch it if its being delt with in 2.0 anyway. But 2.0 could be more then 1 year in the future for all we know right?