Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  API performance

    Posted 10/22/20 02:21 PM

    Hello experts,

    I have developed an API to update Asset and assetspec data in Maximo through API. While testing the performance of API, I noticed that it takes 9326 ms ( 9.3 seconds) to update the data in Maximo when the request payload consists of 17 assets. The dev enviornment consists of 1 JVM.

     

    Is the API performance dependent on the infrastructure sizing ? Are there any guidelines?

     

     

    _____________________________________________________________
    Kushal Desai
    Architect – Maximo
    Linehaul VS

    925.393.8556 (cell)

    in/kushalmd 

    P Please consider the environment before printing this email.

     


    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: API performance

    Posted 10/25/20 07:48 PM
    Hello Kushal,

    As you know Maximo and MIF performance depends of multiple factors. I find following document very useful when I need to look for different ways to improve it. 
    https://www.ibm.com/support/pages/maximo-76-performance-best-practice-guide

    Just some thoughts on the provided information:
    - 17 assets are sent in one payload - I believe it means that they will be update sequentially, one after another
    - I would probably break them down to 1 call per record so they can be processes in parallel - Obviously you would need to create multiple sessions
    - 1 JVM can support on average 50-100 concurrent users (depend on the sizing and what is done by each session)

    How long does it take to process an update of 1 record via front-end? Maybe there are some issues with DB?

    Regards,
    Alexey

    ------------------------------
    Alexey Potanin
    ------------------------------



Related Content