Browse Prior Art Database

Interactive Performance Assistance for BI Reporting Disclosure Number: IPCOM000244531D
Publication Date: 2015-Dec-18
Document File: 5 page(s) / 237K

Publishing Venue

The Prior Art Database


Disclosed is a system to lower the technical threshold for business intelligence reporting in order to facilitate easier development of high performing reports. The novel solution is to use a framework that is built into the report-rendering engine and is designed to provide an interactive performance assistance capability.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 5

Interactive Performance Assistance for BI Reporting

Identifying report performance issues in a reporting system with multiple services in a distributed nature is a challenge due to a system's complexities and concurrencies. Only a few subject matter experts have the ability to identify the optimization options or system bottlenecks, even though high-performing reports are a critical deliverable for many companies.

Traditionally, the following well-known methods and practices are used to address the challenges of delivering high performance reporting:

Performance Logging Program Code Profiling
Half-split (or binary chop) method

The first two methods are mostly used by software engineers who have in-depth product knowledge with goals mostly aimed to improve software performance. A lack of business knowledge hinders the software engineers' ability to improve the data

warehouse model design and develop a fast performing report. The logging and profiling used for this approach is not only impactful to the reporting system, but also becomes a tedious administrative task, as it requires implementation on each service that the reporting system uses.

Business Intelligence (BI) report authors often use the half-split (or binary chop) method. BI report authors have business knowledge but do not have insight into the software product. The BI report authors manually simplify a report by removing one report component at a time until the worst performing component in the report is identified . The next step is to find a work around.

As a report becomes more complicated, identifying the bottleneck becomes more challenging. It is sometimes impossible to simplify a report because that contains multiple interdependencies. The more complex a report is, the more laborious and challenging it becomes for the BI report author.

A method or system is needed that lowers the technical threshold, thus allowing a BI report author to develop a high performing report without requiring traces from the BI Administrator and without the help from subject matter experts .

The novel solution is to use a framework that is built into the report-rendering engine and is designed to provide an interactive performance assistance capability.


Page 02 of 5

A report usually consists of a multitude of layout components. Each layout component in turn contains a physical layout container and a data container. The time spent on rendering a report layout components can be divided conceptually into two categories .

1. Component Time

A. Physical layout render (e.g., Hypertext Markup Language (HTML), Portable Document Format (PDF), Excel*, etc.) time related to font, color, alignment, and pagination

    B. Data retrieval time, including query planning, query execution, and fetching the result set 2. Beginning to End Report Delivery Time: the compl...