We are trying to build a summary at the end of the survey we are making in which they can answer further based on their responses earlier in the survey.
We're seeing page load times on a Amazon EC2 c3.xlarge instance jump from 1-2 seconds to easily 2-3 minutes. This increased load time is happening across all pages, not just the pages the template codes are referenced. The database server is living in a separate EC2 instance. CPU was easily 100% every request on a m3.medium instance but now that we've bumped it up a notch it never exceeds 40%.
In the long term, we'll have to drastically redesign the survey, but in the short term is there anything we can do to alleviate the performance problems? Is there a reason why an exceptionally large question will cause the entire interface to be slower, not just the pages where the question appears?
Basically, we're trying to build a summary at the end of the summary using text arrays.
The summary has three tiers.
In tier 1, there's a title. Tier 1 is a array of texts "question" in Lime Survey. There's about 20 tier 1 questions. A tier 1 question is controlled using a relevancy equation based on previous responses. We currently have them disabled (set to 1) for debugging.
In tier 3, there's a title and an answer box. Tier 3 is the actual fillable row in the array of texts in tier 1. We only show these if they are relevant on previous responses.
Overall, a question will trigger a tier 3 answer to show up, and that will require it's parent tier 2 to show up, and that will trigger the appropriate tier 1 parent to show up.
Help is appreciated, however we have a encroaching deadline so we will not be able to make any major design changes until after our demo.
The administrator has disabled public write access.