Planning Analytics

Planning Analytics

Get AI-infused integrated business planning

 View Only

  • 1.  PAW Transaction Log Query performance

    Posted 09/18/24 07:05 AM

    Hi,

    I do have a support ticket open for this (TS017250981) but since it relates to the demise of the rich tier and more generally to Perspectives itself I thought I would raise it here as well.

    Our PAoC customer is reporting massive increases in Transaction log query times, to the point that the functionality is not usable.

    In Perspectives using the rich tier the response time was 7 seconds, in PAW the response time was 43 minutes.  The query should have been searching over 35 files totalling 600MB.  This is 7 days of files, with a Save Data chore running at a high frequency.

    Is this a known issue with the current implementation as this performance isn't acceptable for such a small query volume.

    In addition, the query when run from PAW was found to be locking, i.e. TI processes were queueing behind it. 

    I can't see a reason for this to be a locking activity, is this by design?

    Cheers!



    ------------------------------
    Steven Rowe
    ------------------------------


  • 2.  RE: PAW Transaction Log Query performance

    Posted 09/18/24 07:13 AM

    HI Steve,

    I can attest to the very slow response times when query the transaction log.

    I was trying to show something recently to a client and gave up after 5 awkward minutes and resorted to FindStr.

    My log file was not huge and I only had the one as this was a non-production environment.

    It was not always this poor but think something recently changed.



    ------------------------------
    George Tonkin
    Business Partner
    MCI Consultants
    Johannesburg
    ------------------------------



  • 3.  RE: PAW Transaction Log Query performance

    Posted 09/19/24 01:11 AM

    For the point around locking. I believe this occurs as it queries the live tm1s.log file or at least affects it in some way. 



    ------------------------------
    Robby Meyers
    ------------------------------

    Original Message


  • 4.  RE: PAW Transaction Log Query performance

    Posted 09/19/24 03:45 AM

    I have tried it on my production PAoC server and our log files are quite large. Even when I only searched for the last 24 hours the query never finished and all my overnight chores were in a wait state behind this never-ending transaction thread. I could not stop the transaction search from the Administrator page and had to raise a IBM Support Case to restart my server as restarting, even the End Process function failed from the Admin page.

    This is a fairly serious concern and we now always revert to searching the log files themselves via a batch process and, as noted by Robby Meyers, we never search the live tm1s.log file due to locking issues.

    I also wonder how TM1 V12 will work as apparently we will not be able to turn off logging per cube in a ti process when we run processes (from what I have heard on webinars) and if we can only see 1500 transaction this feels a little small as all data loaded will be logged.



    ------------------------------
    Douard Le Roux
    ------------------------------



  • 5.  RE: PAW Transaction Log Query performance

    Posted 09/19/24 04:12 AM

    Just to close this out, this is a known issue already being tracked on an APAR, PH61508.



    ------------------------------
    Steven Rowe
    ------------------------------



  • 6.  RE: PAW Transaction Log Query performance
    Best Answer

    Posted 09/19/24 07:11 AM

    We are making some improvements to performance of the transaction log query over REST API.  These changes will be delivered in the next update to TM1 Server.  This will probably be the Planning Analytics 2.0.9.21 release and a corresponding 2.1.x release.

    At the same time we are working on some major improvements to the PAW modeling workbench user interface for transactions logs.  We are introducing lazy loading, so as the modeler scrolls more transaction records from the query will be loaded.  This will allow the modeler to examine more than 1500 transaction records at a time.  There are a few other minor user interface improvements planned as well (e.g searching transactions from multiple users at a time).  These improvements will be delivered in a PAW update before the end of this year.



    ------------------------------
    Stuart King
    Product Manager
    IBM Planning Analytics
    ------------------------------

    Original Message


  • 7.  RE: PAW Transaction Log Query performance

    Posted 09/19/24 08:13 AM

    What would also be very useful is the ability to do a search on "bulk" updates i.e. with change sets with multiple cells affected.

    I would want to be able to search for changes made by George in the last Day/Date Range and then see a list of change sets and times.

    This would narrow down the playing field for those big changes where >1500 cells could have been impacted and allow us to quickly from a list see the change set id relating to changes e.g.

    e8b 2024-09-19 10:01:02
    e9c 2024-09-19 09:15:25

    Typically when someone has made a mistake or has a need to rollback, we could target the log for that user and a rough time, so a list like the above could then allow us to filter further by change set id and roll it all back in one go.



    ------------------------------
    George Tonkin
    Business Partner
    MCI Consultants
    Johannesburg
    ------------------------------

    Original Message


Related Content