The old BW-EML Benchmark was designed for optimizing query throughput only. The BW-AML now introduces a second phase which aims at response time optimization, with strong focus of customer relevant use cases / scenarios.
Main differences/extensions between BW-EML and BW-AML:
- Inserts / Updates / Deletes on transactional data during delta loads
- Master data changes along with delta loads
- Utilization of navigation attributes
- Multiple currencies in source data
- Stand-alone data loads to measure data load times (Phase 2)
- Master data lookups, non-trivial transformations (Phase 2)
- Randomization of selection of key figures, changing set of key figures in navigation step
- More sophisticated use of FEMS queries and exception aggregation
- Currency conversion
- Extension of all queries and navigation steps on multiple part providers
- Different query patterns for Info
- Cube / DSO multiproviders
The BW-AML benchmark consists of 2 phases. Phase 1 is for measuring query throughput at a defined number of initial records. Phase 2 collects information about the runtimes of complex queries and complex delta loads.
The BW-AML benchmark KPIs are for Benchmark Phase 1 the query throughput measured in Advanced Query Navigation Steps / hour. For Phase 2 the 10 complex query runtimes result in the KPI Normalized mean runtime single query test. Finally, the delta load of phase 2 loading, transforming and aggregating 50 Million records results in the Total runtime delta load/transformation test KPI.
Important: Due to the changes in the data model, query design and KPIs the BW-EML and BW-AML benchmark results are not comparable.