•  
      request #13408 Display of a tracker table report can be slow due to a confusion of the MySQL optimizer
    Infos
    #13408
    Thomas Gerbet (tgerbet)
    2019-05-24 14:22
    2019-05-24 13:36
    14158
    Details
    Display of a tracker table report can be slow due to a confusion of the MySQL optimizer
    The SQL query that is built to retrieve the artifacts to display gives both the artifact IDs and the corresponding last changeset IDs as a parameter of the query.
    Besides being not useful (an changeset matching only one artifact) it seems that in some cases, it confuses the MySQL query optimizer resulting in very slow queries and it prevents the report to be displayed because the timeout limits are reached.
    Trackers
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Closed
    2019-05-24
    Attachments
    Empty
    References

    Follow-ups