Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!

The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.

Interface performance degrades as the user increases

Certified Lead Developer

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

Parents
  • 0
    Certified Lead Developer

    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.

Reply
  • 0
    Certified Lead Developer

    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.

Children