Whould someone explain procstat output memory information?












0















I use the command procstat -r $(pidof myprocess) and I get the following output...



  PID COMM             RESOURCE                          VALUE
84867 myprocess user time 00:00:12.637834
84867 myprocess system time 00:00:06.671334
84867 myprocess maximum RSS 11400 KB
84867 myprocess integral shared memory 1931920 KB
84867 myprocess integral unshared data 28272 KB
84867 myprocess integral unshared stack 301568 KB
84867 myprocess page reclaims 653
84867 myprocess page faults 0
...


I am kind of concerned about the huge values of



84867 myprocess       integral shared memory             1 931 920 KB
84867 myprocess integral unshared data 28 272 KB
84867 myprocess integral unshared stack 301 568 KB


What do these three terms mean?



htop gives me decent values about memory (VIRT, etc).

Should I concern about memory leaks?










share|improve this question





























    0















    I use the command procstat -r $(pidof myprocess) and I get the following output...



      PID COMM             RESOURCE                          VALUE
    84867 myprocess user time 00:00:12.637834
    84867 myprocess system time 00:00:06.671334
    84867 myprocess maximum RSS 11400 KB
    84867 myprocess integral shared memory 1931920 KB
    84867 myprocess integral unshared data 28272 KB
    84867 myprocess integral unshared stack 301568 KB
    84867 myprocess page reclaims 653
    84867 myprocess page faults 0
    ...


    I am kind of concerned about the huge values of



    84867 myprocess       integral shared memory             1 931 920 KB
    84867 myprocess integral unshared data 28 272 KB
    84867 myprocess integral unshared stack 301 568 KB


    What do these three terms mean?



    htop gives me decent values about memory (VIRT, etc).

    Should I concern about memory leaks?










    share|improve this question



























      0












      0








      0


      1






      I use the command procstat -r $(pidof myprocess) and I get the following output...



        PID COMM             RESOURCE                          VALUE
      84867 myprocess user time 00:00:12.637834
      84867 myprocess system time 00:00:06.671334
      84867 myprocess maximum RSS 11400 KB
      84867 myprocess integral shared memory 1931920 KB
      84867 myprocess integral unshared data 28272 KB
      84867 myprocess integral unshared stack 301568 KB
      84867 myprocess page reclaims 653
      84867 myprocess page faults 0
      ...


      I am kind of concerned about the huge values of



      84867 myprocess       integral shared memory             1 931 920 KB
      84867 myprocess integral unshared data 28 272 KB
      84867 myprocess integral unshared stack 301 568 KB


      What do these three terms mean?



      htop gives me decent values about memory (VIRT, etc).

      Should I concern about memory leaks?










      share|improve this question
















      I use the command procstat -r $(pidof myprocess) and I get the following output...



        PID COMM             RESOURCE                          VALUE
      84867 myprocess user time 00:00:12.637834
      84867 myprocess system time 00:00:06.671334
      84867 myprocess maximum RSS 11400 KB
      84867 myprocess integral shared memory 1931920 KB
      84867 myprocess integral unshared data 28272 KB
      84867 myprocess integral unshared stack 301568 KB
      84867 myprocess page reclaims 653
      84867 myprocess page faults 0
      ...


      I am kind of concerned about the huge values of



      84867 myprocess       integral shared memory             1 931 920 KB
      84867 myprocess integral unshared data 28 272 KB
      84867 myprocess integral unshared stack 301 568 KB


      What do these three terms mean?



      htop gives me decent values about memory (VIRT, etc).

      Should I concern about memory leaks?







      process freebsd memory proc






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 28 at 11:12







      Vassilis

















      asked Jan 28 at 2:51









      VassilisVassilis

      1012




      1012






















          1 Answer
          1






          active

          oldest

          votes


















          0














          The integral shared memory includes the code and rodata segments of every shared library your program is linked against. That nearly 2GB figure is large, but not totally surprising if it is a big app like a browser. The unshared segments are data that was allocated by your program, including r/w data pages from shared libraries, etc. If these aren't going up alarmingly (or worse, unbounded) you're probably OK.






          share|improve this answer























            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497108%2fwhould-someone-explain-procstat-output-memory-information%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The integral shared memory includes the code and rodata segments of every shared library your program is linked against. That nearly 2GB figure is large, but not totally surprising if it is a big app like a browser. The unshared segments are data that was allocated by your program, including r/w data pages from shared libraries, etc. If these aren't going up alarmingly (or worse, unbounded) you're probably OK.






            share|improve this answer




























              0














              The integral shared memory includes the code and rodata segments of every shared library your program is linked against. That nearly 2GB figure is large, but not totally surprising if it is a big app like a browser. The unshared segments are data that was allocated by your program, including r/w data pages from shared libraries, etc. If these aren't going up alarmingly (or worse, unbounded) you're probably OK.






              share|improve this answer


























                0












                0








                0







                The integral shared memory includes the code and rodata segments of every shared library your program is linked against. That nearly 2GB figure is large, but not totally surprising if it is a big app like a browser. The unshared segments are data that was allocated by your program, including r/w data pages from shared libraries, etc. If these aren't going up alarmingly (or worse, unbounded) you're probably OK.






                share|improve this answer













                The integral shared memory includes the code and rodata segments of every shared library your program is linked against. That nearly 2GB figure is large, but not totally surprising if it is a big app like a browser. The unshared segments are data that was allocated by your program, including r/w data pages from shared libraries, etc. If these aren't going up alarmingly (or worse, unbounded) you're probably OK.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 28 at 19:12









                softweyrsoftweyr

                313




                313






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Unix & Linux Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f497108%2fwhould-someone-explain-procstat-output-memory-information%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    How to make a Squid Proxy server?

                    Is this a new Fibonacci Identity?

                    19世紀