In our application, the landing page displays 1,000 records from a view with 6 or 7 fields. The application performs well for a single user, but performance declines as the number of users increases[goes 12 x slower for 100 users ]. We have reviewed the database calls, and they are quite fast, yet Appian takes a long time to load the pages. Are we missing something here ?
Discussion posts and replies are publicly visible
I agree with what Stefan says here. I will take a guess and say they currently use a spreadsheet and then filter to the data they need.
If you could watch what they currently do and understand their activity maybe there is a way to pre-filter the data, or present it in a far more specific way.
Also, if your data resides in Records, always check to see what you can do with a Record Data Model and support of the Query Record expression before using a view. I have found that a lot of database views can become redundant with the full use of Records.
Hm .. interesting. In my experience, it's almost never a good idea to try to replicate the way how people used to do things in the "old world". There is just too much Excel, Outlook, Phone, Paper, PostIts in there.
It's not necessarily how you will deliver the final solution, it's just a psychological trick to get people to surrender their spreadsheets so if they refuse to use anything other than what they currently have, you can at least provide a baseline to then improve that journey for them through change - most of the time though people are delighted to not have to use their spreadsheets ever again!
That being said, I am sure if you gave them a grid with 1,000 rows in it ... they would download it or try and copy and paste it in to their old spreadsheet!! ... I have seen that happen!!