Power BI OData connections are significantly slowing down Aperture, how to configure to prevent?

KatriM
KatriM Member
in General

Hi,

Our self-service users are using Odata connections to fetch data from Aperture DS to Power BI but that seems to slow down Aperture a lot. During some report executions, it can even prevent logging into Aperture because the log-in window cannot be opened (without any error message).

I can also see several Api Key authentication rows in audit log for each of the Power BI report calls via OData, even as much as about 40 rows of API Key authentications for one report.

How can we configure Odata connections so that there would not be several Api Key authorizations for Odata connections and prevent slowing down that Aperture usage during report executions?

Answers

  • Ian Hayden
    Ian Hayden Experian Super Contributor

    Hi @KatriM,

    Thanks for raising. What would really help us is a Java telemetry file that captures the state of the product over a period of time. If we can get this state captured whilst the product is running slowly, we can analyse the resulting data and find out where it is being held up.

    To capture a telemetry file, please run this from the installation directory, replacing <JavaPID> with the process Id of the Data Studio Java process:

    java64\bin\jcmd <javaPID> JFR.start duration=100s filename=flight.jfr

    After 100 seconds the flight.jfr file will be ready. Please send to me with the associated datastudio and monitor log files, and I'll take a look.

    Many thanks,

    Ian

  • Henry Simms
    Henry Simms Administrator

    The multiple authentication requests you see in the log may be happening because the OData client (PowerBI) is using paging in it's request, which would be recommended when fetching a large amount from a published Data Studio Dataset.

    Data Studio supports $count, $top and $skip parameters to allow clients to page results

Categories