LSF9/LAUA/DB2 performance issues (batch/addins)

Sort:
You are not authorized to post a reply.
Author
Messages
ShawnV
Advanced Member
Posts: 37
Advanced Member

    We are on LSF9 w/LAUA & DB2.  We are experiencing slower performance on both batch & MS Addins. 

    Batch: It appears our Payroll batch process is taking 20% longer. 

    ESS (Pay Checks): Users are receiving timeout errors when they try to access their Statement of Earnings (usually when the system is busy).

    Addins: Even after rewriting our Addins queries, they are running longer (particularly those attempting to access HR type data).

    I personally feel it is somehow related to HR Security and here is why:

    1) I ran a simply Servlet/Router/Data call (the same call the MS Addins makes for a query) to pull back 6000 APVENMAST records -> ran in 5 seconds.  2) I ran an almost identical Data call to pull back 6000 EMPLOYEE records -> ran in 35 seconds.  3) I ran an almost identical Data call to pull back 6000 BNBEN records -> ran in 1:31.

    I then turned off security & ran the BNBEN query again -> ran in 5 seconds.  I then ran the BNBEN query using the old CGI/DME query with Security ON -> ran in 5 seconds.

    Has anyone seen any performance issues running LSF9/LAUA/DB2?  Does anyone have any performance tuning recommendations?  Has anyone seen such poor performance on MS Addins?

    Any help would be appreciated.  Thanks, Shawn

    PS - We are on the latest patches of LSF9.  We are running LSF9.0.3.1 MS Addins.

    PS - Here is the BNBEN query I have been running which takes 1:31: /servlet/Router/Data/Erp?PROD=DEV02&FILE=BNBEN&INDEX=BNBSET1&KEY=100&FIELD=COMPANY;EMPLOYEE&OUT=CSV&DELIM=%09&NOHEADER=TRUE&NEXT=TRUE&MAX=6000

    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
      When did the slow down happen?

      Is your addin connnect via your portal server or your application server?
      ShawnV
      Advanced Member
      Posts: 37
      Advanced Member
        I can't be sure but I believe the slow down has always be there. The users are stating they did not see the slow response in our development environment, but I don't think they tested them there. We can recreate the slow response times in our development environment.

        The BNBEN query listed above was run directly from the Portal URL (it is the exact same call that MS Addins makes behind the scenes). If anyone else is on LSF9, would you be able to run the query above from your Portal URL and let me know how long it takes for your query to come back.
        Jimmy Chiu
        Veteran Member
        Posts: 641
        Veteran Member
          Are you on System i? Windows?
          ShawnV
          Advanced Member
          Posts: 37
          Advanced Member
            UNIX
            mark.cook
            Veteran Member
            Posts: 444
            Veteran Member
              Are you seeing anything in your websphere logs related to hung threads, etc? Also since your users are just starting to complain about it, take a look back at the jobs payroll batch jobs that have been run to see if you can see where the time increase started. It could be related to an install of a patch of some kind. You can at least get an idea of if it was always there or something new.

              When we first went up on LSF9 over a year ago we had performance issues, webspere issues, etc. We were seeing hung threads in our logs that eventually brought the system to its knees. After weekly calls with Lawson, we tweeked our websphere configuration, adjusted our MSCM filter properties file for the data calls to not all kick off on the same second, and broke out some data calls in websphere to another jvm and that seemed to do the trick for us.

              You are not authorized to post a reply.