View source for Optimizing an application's performance

== Memory ==
The memory footprint of a user is determined by the size of individual cases multiplied by the number of cases that are open during a working session. Memory footprint on the server is critical for sizing a system to accommodate expected user load while leaving sufficient head room for occasional traffic spikes.  Out of  Memory errors cause nodes to crash and result in disruptions to end users who lose work in progress.

Use the “Performance” tool in Developer Studio to examine the clipboard (memory) usage from screen to screen. Identify key scenarios and evaluate them step by step to examine memory usage. Run this twice to validate that memory utilization is consistent to ensure there are no leaks caused by pages accumulating in memory.

'''Steps''' 

* Reset the performance data
* Execute the first screen in your scenario
* Utilize the “Add reading with clipboard size” button
* Open the delta snapshot that was last added and examine the requestor clipboard size to determine if it is in threshold.
* Repeat this process for each screen in the scenario.
 

==== '''Metric: Requestor Clipboard Size''' ====

Threshold: Clipboard sizes greater than 5 MB are worthy of closer examination.

Remediation:  Investigate large pages and their payload to determine business value of data. Data retrieval is expensive and often more data is retrieved than needed to fulfill a business requirement. Report definitions used to retrieve data should be examined to ensure they are using an optimized WHERE clause that returns only the data needed. Explicitly removing temporary pages (created say for running reports or fetching external data) reduces memory footprint.