•  
      request #8676 Tracker Performance Issue. Artifact retrievement takes 60 seconds
    Infos
    #8676
    Peter Struck (p3t3rstruck)
    2016-01-15 17:45
    2015-12-08 09:17
    8789
    Details
    Tracker Performance Issue. Artifact retrievement takes 60 seconds
    Our Tuleap instance is getting slow ...
    we have one 2 big projects fed with 3-7 Tracker.
    One project has ~ 100 Artifacts
    The other one has ~ 150 Artifacts

    now whenever and no matter what project (we have a few one with only one tasks tracker) the report which lists the artifacts as soon as so click on the tracker takes > 10s

    We made the agile approach and have sprints which calculate the efforts.
    All computed fields have the option fast computation.
    The Agile Dashboard even takes about 60s.

    Pls give me a few tips what kind of info i can provide for you?
    log files?
    sql query times?
    ...

    the requests from clientside are:
    http://cbasealm.ads.dlh.de/plugins/agiledashboard/?group_id=101 = 58 seconds
    http://cbasealm.ads.dlh.de/plugins/tracker/?tracker=89 = 10 seconds


    Trackers
    8.9
    CentOS 6
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Empty
    New
    Empty
    Attachments
    Empty
    References
    Referencing request #8676

    Follow-ups

    User avatar
    When ES is available, you have a new input in the advanced search to perform a query in the comments.
    User avatar
    But you cannot select the comments (Follow-ups) as a search criteria from dropdown? so how the will be touched by elasticsearch when searching in trackers?
    User avatar
    It's because ElasticSearch can be used to search in comments in the Tracker Report search form.

    Does it answer your question ?
    User avatar
    slow query log with 1 second long_query_time shows that everything with the DB is fine! --> no log entries - (tested with select sleep)

    What else could be the problem when not DB??
    User avatar
    You should activate slow query logging in mysql configuration in order to
    see if a particular query is responsible for such performance issue. Tuleap
    can handle pretty well many artfiacts so there is obviously a problem with
    your instance.
    User avatar
    Hi Peter,

    Could you please run the following command:

    mysqlcheck -Aao -u codendiadm -p

    Does it improves something?

    Best regards,
    Nicolas Terray
    User avatar
    debug.log:
    2015-12-08T09:29:44+01:00 Tracker_Report::getMatchingIdsInDb -> searching for {"user":"u524036","project":"101","query":{"number":"","status":[],"description":"","summary":"","release":[],"assigned_to_lhind":[]},"trackers":["89"]}
    2015-12-08T09:29:44+01:00 Tracker_Report::getMatchingIdsInDb -> Nb matching: 75
    2015-12-08T09:29:44+01:00 Tracker_Report::getMatchingIdsInDb -> Time taken: 0.016754865646362 seconds