Results 1 to 5 of 5

Thread: Inexplicably long runtimes despite small amount of data.

Threaded View

Previous Post Previous Post   Next Post Next Post
  1. #1
    Conjurer pinarello's Avatar
    Join Date
    Jun 2019
    Location
    Germany
    Posts
    156
    Articles
    0
    Excel Version
    Office 365

    Inexplicably long runtimes despite small amount of data.

    I have a Power Query application, with very little data, but it always runs the first 1-3 times, after opening, for a very long time, up to 100 seconds on my desktop, to update the data (work_occupancy_schedule). After that, the runtime is relatively normal.

    The recalculation is triggered by pressing the button "Refresh Belegungsplan", or the selection of another calendar week.

    The purpose is to create a weekly attendance plan for kindergarten and after-school children ("Kita" and "Hort" spreadsheets). Holidays ("Freie Tage") and temporarily deviating attendances ("Kita temporär" and "Hort temporär") are taken into account.In the list, the children per group are displayed in ascending order according to the planned arrival time and, depending on the determined time of day, are displayed on the left, in the middle or on the right for each day and the minimum number of rows per group is also taken into account.
    In the list, the children per group are displayed in ascending order according to the planned arrival time and, depending on the determined time of day, are displayed on the left, in the middle or on the right for each day and the minimum number of rows per group is also taken into account.


    In order to achieve the final display, an overall list (query "Liste_Kita_und_Hort") is created after preparation of all data, from which the individual lists are then created and displayed according to the respective color bars.

    In principle, it would also be possible without any problem to create the rows for the color bars within the queries in order to then generate the color markings using conditional formatting. But this would have no influence on the too long runtimes, because this is created in one of the upstream queries. But since it is not possible to set timestamps within a query, I unfortunately cannot find out why the whole process runs so long after opening. I also don't have the impression that I am using functions that are known for long runtimes.

    But maybe someone, with enough experience, has an idea which command is responsible for the long runtimes, or can give me a hint how to find out myself.

    I would like to mention, that this is a question, which was asked by a kindergarten from Switzerland, in a German forum. The link to post is included in the folder.
    Attached Files Attached Files

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •