Topic
  • 5 replies
  • Latest Post - ‏2012-10-03T16:42:26Z by SystemAdmin
VeljkoC
VeljkoC
82 Posts

Pinned topic MAXIMO too slow after importing large number of tickets

‏2012-09-27T07:22:59Z |
Hi,

I imported over 200000 (closed) tickets in Maximo.
Now Maximo is really slow.
CPU and memory usage are still very well not over 30%.

Default query for ticket app is to show only open but still working with application is to slow.
Do someone have experience working with large number of tickets in the system and slow performance?
What to do to make it faster?
I will really appreciate some help.

BR
Updated on 2012-10-03T16:42:26Z at 2012-10-03T16:42:26Z by SystemAdmin
  • gulfsoft
    gulfsoft
    72 Posts

    Re: MAXIMO too slow after importing large number of tickets

    ‏2012-09-27T08:23:44Z  
    Google "Maximo database tuning" to get links on tuning your database, depending on which DB and version you're using.

    We can make Tivoli software work for you!www.gulfsoft.com
  • bportaluri
    bportaluri
    67 Posts

    Re: MAXIMO too slow after importing large number of tickets

    ‏2012-09-27T15:37:18Z  
    Lots of useful information in the Maximo IBM Wiki.
    200000 (closed) tickets are not too many. I have seen few millions of work orders in Maximo environments working quite well.
    If CPU consumption on the app server is not high the problem should be in the DB.
    Keep in mind that you have to monitor each CPU core separately. Java cannot split the CPU workload across multiple cores for each user request. If you have a 4-core CPU and there is only one user connected you will never see CPU consumption higher than 25% (apart from background cron tasks and escalations).

    Regards, Bruno
  • VeljkoC
    VeljkoC
    82 Posts

    Re: MAXIMO too slow after importing large number of tickets

    ‏2012-09-28T09:26:32Z  
    Lots of useful information in the Maximo IBM Wiki.
    200000 (closed) tickets are not too many. I have seen few millions of work orders in Maximo environments working quite well.
    If CPU consumption on the app server is not high the problem should be in the DB.
    Keep in mind that you have to monitor each CPU core separately. Java cannot split the CPU workload across multiple cores for each user request. If you have a 4-core CPU and there is only one user connected you will never see CPU consumption higher than 25% (apart from background cron tasks and escalations).

    Regards, Bruno
    Bruno thanks for reply so what is your suggestions for database tuning?

    I only found this.
    https://www-304.ibm.com/support/docview.wss?uid=swg21451593

    DB2_EVALUNCOMMITTED
    DB2_SKIPDELETED
    DB2_SKIPINSERTED

    I set them on ON.

    https://www-304.ibm.com/support/docview.wss?uid=swg21421645
    Also I found this but my parameters are similar set as in link.

    So do you please know some concrete more tuning stuff which I can do on database?
    You are probably right it is problem with database because in DBVisualizer every time I want to connect to database it takes up to long 10 seconds (while in some other environments it takes only 1 second)

    Thank you very much
  • swkim90049
    swkim90049
    437 Posts

    Re: MAXIMO too slow after importing large number of tickets

    ‏2012-10-01T23:08:55Z  
    Look at http://www-01.ibm.com/support/docview.wss?uid=swg21291250

    mxe.db.logSQLTimeLimit=1000

    When you review your maximo.log, you can possibly see which queries are taking a long time.

    I'm not familiar with DB2, but you may want to review the query and if it is utilizing the current indexes optimally. If you have customer queries, you may see benefit from creating a new index... although when you update records, all indexes have to be touched during the update which is a performance lag.
  • SystemAdmin
    SystemAdmin
    5842 Posts

    Re: MAXIMO too slow after importing large number of tickets

    ‏2012-10-03T16:42:26Z  
    You might also want to check out the best practices for performance white papers that are available for download. They have information related to tuning the database as well as maintaining it for best performance.

    The version for Maximo 7.1.1.x releases is located at:
    https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=a9ba1efe-b731-4317-9724-a181d6155e3a#fullpageWidgetId=W5f281fe58c09_49c7_9fa4_e094f86b7e98&file=8a16c9a5-a6c7-4b5e-aa44-e270fa0117cb

    And the version for Maximo 7.5.x releases is located at:
    https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/communityview?communityUuid=a9ba1efe-b731-4317-9724-a181d6155e3a#fullpageWidgetId=W5f281fe58c09_49c7_9fa4_e094f86b7e98&file=c51d5f5b-dea3-4043-a81f-d5213fc10063