Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-28265

Trending view for increaded/decreased memory consumption (Praqma case 12991)

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      We use the memory-map-plugin to track the memory consumption of our embedded software over time. Basically it's purpose is a svn/git-blame for memory: "Hey Peter, svn commit <xy> took 500 bytes of fast memory!"
      Therefore it would be pretty handy to have a trending graph like the SLOC (lines of code) plugin provides.

      Example1: how SLOC looks like
      https://wiki.jenkins-ci.org/download/attachments/37322820/cloc_trend.png

      Example2: how our memory usage looks like, you can tell that there's something happening, but you can't really tell how mouch in bytes
      (attachment)

        Attachments

          Activity

          Hide
          bue Bue Petersen added a comment -

          Examples of delta stats on build and job page.

          Show
          bue Bue Petersen added a comment - Examples of delta stats on build and job page.
          Hide
          bue Bue Petersen added a comment -

          Hi Florian

          Thanks once again for interacting with us regarding the plugin.

          Can you help me understand your request, I'm not sure I get it all right.
          As I understand it, what you miss is the delta graph? That is a graph like the "Lines of code (delta)" in your example https://wiki.jenkins-ci.org/download/attachments/37322820/cloc_trend.png ?
          That is because our current graph is hard to read, if you want to see if there is added 5Kbytes or 8 kBytes new memory use - right?

          I think there is a good use-case for such deltas - we already also have logged this issue, about showing deltas on the build page and/or job page - see JENKINS-18245
          Such deltas could, beside the graph you suggest, could follow the same concepts like the analytics plugins - see pictures.

          We also hope to continue the work soon on the plugin and concept, and you might especially find the what we have called third and fourth development iteration interesting (https://wiki.jenkins-ci.org/display/JENKINS/Memory+Map+Plugin#MemoryMapPlugin-Thirdandfourthdevelopmentiteration).
          Basically this is a drill down feature, so image to click on the graph dive down into the details on what actual code uses that memory and in which sections are it used. For example inspired by the Cobertura coverage plugin drill down feature, showing details like this: https://issues.jenkins-ci.org/secure/thumbnail/18656/_thumb_18656.png

          Show
          bue Bue Petersen added a comment - Hi Florian Thanks once again for interacting with us regarding the plugin. Can you help me understand your request, I'm not sure I get it all right. As I understand it, what you miss is the delta graph? That is a graph like the "Lines of code (delta)" in your example https://wiki.jenkins-ci.org/download/attachments/37322820/cloc_trend.png ? That is because our current graph is hard to read, if you want to see if there is added 5Kbytes or 8 kBytes new memory use - right? I think there is a good use-case for such deltas - we already also have logged this issue, about showing deltas on the build page and/or job page - see JENKINS-18245 Such deltas could, beside the graph you suggest, could follow the same concepts like the analytics plugins - see pictures. We also hope to continue the work soon on the plugin and concept, and you might especially find the what we have called third and fourth development iteration interesting ( https://wiki.jenkins-ci.org/display/JENKINS/Memory+Map+Plugin#MemoryMapPlugin-Thirdandfourthdevelopmentiteration ). Basically this is a drill down feature, so image to click on the graph dive down into the details on what actual code uses that memory and in which sections are it used. For example inspired by the Cobertura coverage plugin drill down feature, showing details like this: https://issues.jenkins-ci.org/secure/thumbnail/18656/_thumb_18656.png
          Hide
          freinhard Florian Reinhard added a comment -

          Hi Bue,

          yes you understood my request perfectly right! A delta table like cppcheck and/or a graph like the "Lines of code (delta)" would be my desire!

          Sorry for filing a dupe of JENKINS-18245. Only difference: i'd call this feature "major" and not "minor"

          Show
          freinhard Florian Reinhard added a comment - Hi Bue, yes you understood my request perfectly right! A delta table like cppcheck and/or a graph like the "Lines of code (delta)" would be my desire! Sorry for filing a dupe of JENKINS-18245 . Only difference: i'd call this feature "major" and not "minor"
          Hide
          bue Bue Petersen added a comment -

          Great, we have the same understanding.

          No problem, it is not a directly duplicate, as I think your delta graph is good for this issue and then we do the delta stats on build and job page as part of JENKINS-18245.

          I would like to have both.

          Show
          bue Bue Petersen added a comment - Great, we have the same understanding. No problem, it is not a directly duplicate, as I think your delta graph is good for this issue and then we do the delta stats on build and job page as part of JENKINS-18245 . I would like to have both.
          Hide
          bue Bue Petersen added a comment -

          Represented by GHI https://github.com/Praqma/memory-map-plugin/issues/7

           

          We only use Github issue going forward.

          Show
          bue Bue Petersen added a comment - Represented by GHI https://github.com/Praqma/memory-map-plugin/issues/7   We only use Github issue going forward.

            People

            Assignee:
            praqma Praqma Support
            Reporter:
            freinhard Florian Reinhard
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: