For 2.3, a focused effort on KRAD will be undertaken to accomplish the following goals:
Once performance metrics and benchmarks are collected they will be documented and used to gauge progress. After each phase of work a new set of performance metrics will be collected.
Tuning needs to occur both with server side and client side code. A good amount of previous profiling has already been done to identify the bottlenecks server side:
The majority of tasks will focus on lowering the costs of these functions. Also, the performance in these areas degrades quickly when using collections. Therefore initial efforts will focus on views with collections (although improvements here should bring improvements for non-collection views).
The major bottlenecks with client side code have not been identified yet. Therefore the first priority here will be to identify those and then explore potential fixes.
The QA team will collect benchmark data from KRAD applications that will be used to guide the performance effort. In addition, the KRAD team will work with other applications to determine where the bottlenecks are and verify they are accounted for in the work plan.
Work with consultants to fine tune and determine optimal deployment configuration.