https://community.appian.com/success/w/article/3216/performance-and-load-testingen-USTelligent Community 12https://community.appian.com/success/w/article/3216/performance-and-load-testingMon, 30 Dec 2024 18:34:47 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62joel.larinhttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsCurrent Revision posted to Article by joel.larin on 12/30/2024 6:34:47 PM<br /> <div> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/guide/3317/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/guide/3324/best-practices-database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/guide/3215/performance-testing-methodology#configure_the_performance_test_environment">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using the <a href="/b/appmarket/posts/appian-locust">Appian Locust</a> tool, which uses the open source <a href="https://locust.io">Locust</a> load testing framework. It provides an easy, programmatic way to develop and execute load and performance tests for Appian. Alternatively, you can use standard web application performance testing tools. These include JMeter and LoadRunner.</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery, testing, Platform</div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/8Mon, 30 Dec 2024 18:34:20 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62joel.larinhttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 8 posted to Article by joel.larin on 12/30/2024 6:34:20 PM<br /> <div> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/guide/3317/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/guide/3324/best-practices-database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/guide/3215/performance-testing-methodology#configure_the_performance_test_environment">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using the Appian Locust tool, which uses the open source <a href="https://locust.io">Locust</a> load testing framework. It provides an easy, programmatic way to develop and execute load and performance tests for Appian. Alternatively, you can use standard web application performance testing tools. These include JMeter and LoadRunner.</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery, testing, Platform</div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/7Thu, 18 Apr 2024 15:55:42 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62Appian Max Teamhttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 7 posted to Article by Appian Max Team on 4/18/2024 3:55:42 PM<br /> <div> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/guide/3317/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/guide/3324/best-practices-database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/guide/3215/performance-testing-methodology#configure_the_performance_test_environment">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using standard web application performance testing tools. These include <a href="http://jmeter.apache.org/">JMeter </a>and <a href="https://www.microfocus.com/en-us/products/loadrunner-professional/overview">LoadRunner</a>. Performance test with the framework your team has the most experience with.&nbsp;</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery, testing, Platform</div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/6Tue, 31 Oct 2023 19:57:29 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62matt.cosenzahttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 6 posted to Article by matt.cosenza on 10/31/2023 7:57:29 PM<br /> <div> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/guide/3317/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/guide/3324/best-practices-database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/guide/3215/performance-testing-methodology#configure_the_performance_test_environment">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using standard web application performance testing tools. These include <a href="http://jmeter.apache.org/">JMeter </a>and <a href="https://www.microfocus.com/en-us/products/loadrunner-professional/overview">LoadRunner</a>. Performance test with the framework your team has the most experience with.&nbsp;</p> </div><div style="clear:both;"></div> <div style="font-size: 90%;">Tags: Delivery, testing, Platform</div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/5Tue, 31 Oct 2023 19:56:56 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62matt.cosenzahttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 5 posted to Article by matt.cosenza on 10/31/2023 7:56:56 PM<br /> <div> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/guide/3317/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/guide/3324/best-practices-database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/guide/3215/performance-testing-methodology#configure_the_performance_test_environment">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using standard web application performance testing tools. These include <a href="http://jmeter.apache.org/">JMeter </a>and <a href="https://www.microfocus.com/en-us/products/loadrunner-professional/overview">LoadRunner</a>. Performance test with the framework your team has the most experience with.&nbsp;</p> </div><div style="clear:both;"></div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/4Thu, 05 Oct 2023 17:59:34 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62Appian Max Teamhttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 4 posted to Article by Appian Max Team on 10/5/2023 5:59:34 PM<br /> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/the-appian-playbook/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/the-appian-playbook/1463/database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/guide/3215/performance-testing-methodology">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using standard web application performance testing tools. These include <a href="http://jmeter.apache.org/">JMeter </a>and <a href="https://www.microfocus.com/en-us/products/loadrunner-professional/overview">LoadRunner</a>. Performance test with the framework your team has the most experience with.&nbsp;</p><div style="clear:both;"></div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/3Thu, 27 Jul 2023 17:09:44 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62joel.larinhttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 3 posted to Article by joel.larin on 7/27/2023 5:09:44 PM<br /> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/the-appian-playbook/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/the-appian-playbook/1463/database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/guide/3215/performance-testing-methodology">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using standard web application performance testing tools. These include <a href="http://jmeter.apache.org/">JMeter </a>and <a href="https://www.microfocus.com/en-us/products/loadrunner-professional/overview">LoadRunner</a>. Performance test with the framework your team has the most experience with.&nbsp;</p><div style="clear:both;"></div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/2Thu, 27 Jul 2023 17:03:16 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62joel.larinhttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 2 posted to Article by joel.larin on 7/27/2023 5:03:16 PM<br /> <div> <h3>Why Performance Test?</h3> <p>Performance testing can be used to answer critical questions about the application, such as:</p> <ul> <li>Will pages load fast enough to satisfy end users?</li> <li>Can the application store all of the data that will be collected?</li> <li>Will performance be consistent over time?</li> <li>Which areas of my application should I improve?</li> </ul> <p>Answering these types of questions reduces risk, informs current business decisions and assists future planning. Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/the-appian-playbook/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</p> <h3>Process Performance Baseline</h3> <p>When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing. Performance of individual activities is recorded in logs, and designers can utilize the <a href="https://docs.appian.com/suite/help/latest/health-check.html">Appian Health Check</a> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze <a href="https://docs.appian.com/suite/help/latest/Logging.html">Appian Logs</a> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp; Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</p> <h3>Performance Testing</h3> <p>Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</p> <p>There are two load factors to consider during performance testing:</p> <ul> <li>Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the <a href="/w/the-appian-playbook/1463/database-volume-testing">Database Volume Testing</a> play for tips on how to load data into your environment.</li> <li>Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</li> </ul> <p>More details on methodology, complete with test design templates and helpful tips, can be found under <a href="/w/the-appian-playbook/performance-testing-methodology">Performance Testing Methodology</a>.</p> <p>Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</p> <h3>Tools</h3> <p>You can execute performance tests using standard web application performance testing tools. These include <a href="http://jmeter.apache.org/">JMeter </a>and <a href="https://www.microfocus.com/en-us/products/loadrunner-professional/overview">LoadRunner</a>. Performance test with the framework your team has the most experience with.&nbsp;</p> </div><div style="clear:both;"></div> https://community.appian.com/success/w/article/3216/performance-and-load-testing/revision/1Thu, 27 Jul 2023 16:57:52 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:fee595c7-b5d5-492b-9d68-5c91486b7f62joel.larinhttps://community.appian.com/success/w/article/3216/performance-and-load-testing#commentsRevision 1 posted to Article by joel.larin on 7/27/2023 4:57:52 PM<br /> <div> <h3><span style="font-size:150%;font-weight:400;">Why Performance Test?</span></h3> <p><span style="font-size:inherit;font-weight:400;">Performance testing can be used to answer critical questions about the application, such as:</span></p> <ul> <li><span style="font-family:inherit;font-size:inherit;">Will pages load fast enough to satisfy end users?</span></li> <li><span style="font-family:inherit;font-size:inherit;font-weight:400;">Can the application store all of the data that will be collected?</span></li> <li><span style="font-family:inherit;font-size:inherit;font-weight:400;">Will performance be consistent over time?</span></li> <li><span style="font-family:inherit;font-size:inherit;font-weight:400;">Which areas of my application should I improve?</span></li> </ul> <p><span style="font-size:inherit;"><span style="font-weight:400;">Answering these types of questions reduces risk, informs current business decisions and assists future planning.</span> <span style="font-weight:400;">Performance testing is needed to determine if the application will perform within specification given a particular situation. It also validates if the resources provided to the application are sufficient for the given volume and data load. The &quot;right&quot; amount of performance testing can only be determined by the project sponsor and stakeholders after considering the importance or visibility of the application, potential revenue loss due to poor performance, and other risk factors.Appian designers should ensure that end user interfaces perform within the specification before they promote the feature to higher environments. If interfaces do not perform adequately during unit testing, they will not improve during performance testing. There are several ways that interface performance can be captured and various troubleshooting techniques. Please see <a href="/w/the-appian-playbook/interface-performance-and-debugging">Interface Performance and Debugging</a> for more details.</span></span></p> <h3><span style="font-size:150%;font-weight:400;">Process Performance Baseline</span></h3> <p><span style="font-size:inherit;"><span style="font-weight:400;">When designing process models, designers need to pay attention to the response times between user tasks to ensure appropriate user experience. Similarly to interfaces, processes need to perform appropriately during unit tests, before they can be accepted for performance testing.</span> <span style="font-weight:400;">Performance of individual activities is recorded in logs, and designers can utilize the </span><a href="https://docs.appian.com/suite/help/latest/health-check.html"><span style="font-weight:400;">Appian Health Check</span></a><span style="font-weight:400;"> to find out if there were any expressions or smart services that could impact end users&rsquo; experience. Health Check also provides an HTTP Response Time chart that provides an aggregate view of performance within the environment. These tools should be utilized after every round of functional testing to monitor emerging performance risks. Absence of Health Check should not be a blocker to analyze performance test results. You can still analyze </span><a href="https://docs.appian.com/suite/help/latest/Logging.html"><span style="font-weight:400;">Appian Logs</span></a><span style="font-weight:400;"> in their tool of choice (Splunk, SolarWinds, Grafana, New Relic, Excel).&nbsp;</span> <span style="font-weight:400;">Additionally, designers can use network monitoring tools built into their browser, to record the exact performance of requests between user clicks during their unit testing.</span></span></p> <h3><span style="font-size:150%;font-weight:400;">Performance Testing</span></h3> <p><span style="font-size:inherit;font-weight:400;">Performance testing should be done once the application is in a stable build with the majority of the functionality built out. The app does not have to be complete to get started, but needs to pass the QA/QC cycle, so that performance results are not skewed by application errors. Additionally, performance testing needs to be executed for major releases of the application. Over time, the test will grow to include additional applications and functionality as your platform use evolves.</span></p> <p><span style="font-size:inherit;font-weight:400;">There are two load factors to consider during performance testing:</span></p> <ul> <li style="font-weight:400;"><span style="font-size:inherit;"><span style="font-weight:400;">Data Load - how much data is in the system during performance testing? This is a frequently overlooked factor but applications need to be tested with a pre-loaded set of data in order to ascertain how it will perform in a realistic situation. Performance testing is often executed with blank databases, which will not be the case 3, 6, 12 months or even at application go-live. Results from such testing will be inaccurate.&nbsp; Please read the </span><a href="/w/the-appian-playbook/1463/database-volume-testing"><span style="font-weight:400;">Database Volume Testing</span></a><span style="font-weight:400;"> play for tips on how to load data into your environment.</span></span></li> <li style="font-weight:400;"><span style="font-size:inherit;font-weight:400;">Load Volume - how many users are in the system creating transactions? When designing your test, you need to find out how many business processes are executed in a given timeframe by how many users. You also need to make sure that all other significant activity in the system is tested, to set up a realistic transaction volume scenario. Tests need to be designed to emulate real user activity, with appropriate pauses between interactions.</span></li> </ul> <p><span style="font-size:inherit;"><span style="font-weight:400;">More details on methodology, complete with test design templates and helpful tips, can be found under </span><a href="/w/the-appian-playbook/performance-testing-methodology"><span style="font-weight:400;">Performance Testing Methodology</span></a><span style="font-weight:400;">.</span></span></p> <p><span style="font-size:inherit;font-weight:400;">Performance testing should have its own project plan and it should be considered its own agile project. A backlog of performance improvement fixes will start to build with each nightly performance test run. The business should prioritize the improvements based on impact and severity. Promote performance fixes on a nightly basis and rerun the performance test to determine the impact of each change.&nbsp;</span></p> <h3><span style="font-size:150%;font-weight:400;">Tools</span></h3> <p><span style="font-size:inherit;"><span style="font-weight:400;">You can execute performance tests using standard web application performance testing tools. These include </span><a href="http://jmeter.apache.org/"><span style="font-weight:400;">JMeter </span></a><span style="font-weight:400;">and </span><a href="https://www.microfocus.com/en-us/products/loadrunner-professional/overview"><span style="font-weight:400;">LoadRunner</span></a><span style="font-weight:400;">. Performance test with the framework your team has the most experience with.&nbsp;</span></span></p> </div><div style="clear:both;"></div>