Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-38921

Performance regression of AnimatedImage

    XMLWordPrintable

Details

    • I7ab0b5f47ecec6cb3cdded0dd219d6acc1bc4148

    Description

      Since QtQuick2, the AnimatedImage component is less efficient than it was with QtQuick1. In fact, it uses more CPU and memory to work properly.

      To point out the issue, I made two similar applications, the first one using QtQuick1.1 and the second one using QtQuick 2.2. I compiled both applications with Qt 5.3.0 RC1 for Windows (MinGW) and I got the following results with a Intel Core i7-3610QM 2.3 GHz processor and a NVidia GeForce 670M GTX graphic card :

      • QtQuick1.1 : 0% of CPU, 22Mo of RAM
      • QtQuick2.2 : 5% of all my threads (if you combine, it represents 40% of one thread), 54Mo of RAM.

      I think the RAM usage is not really important (it just requires AnimatedImage to use a cache system), but the CPU usage may be really embarrassing on mobile platform. It's probably related to the scene graph.

      Please feel free to ask more information if you need.

      Attachments

        1. Performance-test-QtQuick1.1.zip
          9 kB
          Louis du Verdier
        2. Performance-test-QtQuick2.2.zip
          6 kB
          Louis du Verdier
        3. Performance-test-QtQuick2.2-AnimatedSprite.zip
          6 kB
          Louis du Verdier

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-64272 AnimatedImage uses a lot of memory when caching is enabled

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-70730 When an AnimatedImage is continually running then it can end up crashing due to lack of memory

          • P1: Critical - Urgent and Important, will STOP the release if matched with set FixVersion field. This includes regressions from the last version that are not edge cases; Data loss; Build issues; Flaky tests; All but the most unlikely crashes/lockups/hanging; Serious usability issues and embarrassing bugs & Bugs critical to a deliverable. This is the highest possible priority for requirements.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-31872 AnimatedImage crashes with GIF

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-39217 Animated image loaded from network produces warnings

          • P3: Somewhat important - Should be fixed, but doesn't affect the release in any way.
          • Closed
          resulted in

          Bug - A problem which impairs or prevents the functions of the product. QTBUG-64272 AnimatedImage uses a lot of memory when caching is enabled

          • P2: Important - Urgent, should be fixed, but will not stop the release.
          • Open
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              sletta Gunnar Sletta
              amnell Louis du Verdier
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes