Segment length calculation was not working due not updated metaCache

XMLWordPrintable

      problem

      The segment length calculation in one trans-unit is not working correctly, due necessary performance optimization in TRANSLATE-1310.

      reason

      For performance reasons the SQL to update the metaCache was changed to be restricted to one segment. This is wrong at that place. The change must be removed.

      research

      To reimprove the performance again - after removing the above mentioned change - some DB indexes must be changed. This was very interesting, since the following makes a difference:

      • having two separate indexes on two columns
      • or having one index over both columns

      The first case was working on my mariaDB via index_merge. On our server and a customers server the automatic merge was not done, and the combined index is the better solution. In addition the different amount of data in the tables on all three systems makes it impossible to compare the query optimization one by one.

            Assignee:
            Thomas Lauria
            Reporter:
            Thomas Lauria
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: