JVM metaspace is filled after minor garbage collection





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







1















I have been looking into Java memory management and various sections in the heap memory like eden, s0, s1, old gen and metaspace. I was using VisualGC for tracking how memory is filled among different sections of heap. I noticed there is a sharp increase in the amount of memory occupied in the metaspace area after first garbage collection.



Here's an image of the VisualGC representation:



VisualGC_Monitoring



I would like to understand what gets added to metaspace after the first gc. I did research but couldn't get answers. Any help here?










share|improve this question































    1















    I have been looking into Java memory management and various sections in the heap memory like eden, s0, s1, old gen and metaspace. I was using VisualGC for tracking how memory is filled among different sections of heap. I noticed there is a sharp increase in the amount of memory occupied in the metaspace area after first garbage collection.



    Here's an image of the VisualGC representation:



    VisualGC_Monitoring



    I would like to understand what gets added to metaspace after the first gc. I did research but couldn't get answers. Any help here?










    share|improve this question



























      1












      1








      1








      I have been looking into Java memory management and various sections in the heap memory like eden, s0, s1, old gen and metaspace. I was using VisualGC for tracking how memory is filled among different sections of heap. I noticed there is a sharp increase in the amount of memory occupied in the metaspace area after first garbage collection.



      Here's an image of the VisualGC representation:



      VisualGC_Monitoring



      I would like to understand what gets added to metaspace after the first gc. I did research but couldn't get answers. Any help here?










      share|improve this question
















      I have been looking into Java memory management and various sections in the heap memory like eden, s0, s1, old gen and metaspace. I was using VisualGC for tracking how memory is filled among different sections of heap. I noticed there is a sharp increase in the amount of memory occupied in the metaspace area after first garbage collection.



      Here's an image of the VisualGC representation:



      VisualGC_Monitoring



      I would like to understand what gets added to metaspace after the first gc. I did research but couldn't get answers. Any help here?







      java garbage-collection heap-memory visualvm metaspace






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 23 '18 at 18:24









      Slaw

      10.3k31235




      10.3k31235










      asked Nov 23 '18 at 17:36









      meesunmeesun

      213




      213
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Metaspace is not "full". According to the captions, the limit for metaspace is 1.008G but you have 8.602M in there (out of a 9.125M initial allocation). That is about 1% of the limit.



          Metaspace contains things related to classes; i.e. bytecodes, compiled native code, descriptors, statics. ~8M bytes is quite a modest amount of metaspace for a typical Java application that pulls in a few Java SE or 3rd-party library classes.




          I would like to understand what gets added to metaspace after the first gc.




          I suspect that it is just an accounting thing; i.e. the amount of memory used by metaspace only gets updated when the GC runs. If you notice, the 2 apparent changes in metaspace usage (after the start of recording) both coincide with a GC event.






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            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: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            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%2fstackoverflow.com%2fquestions%2f53450931%2fjvm-metaspace-is-filled-after-minor-garbage-collection%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














            Metaspace is not "full". According to the captions, the limit for metaspace is 1.008G but you have 8.602M in there (out of a 9.125M initial allocation). That is about 1% of the limit.



            Metaspace contains things related to classes; i.e. bytecodes, compiled native code, descriptors, statics. ~8M bytes is quite a modest amount of metaspace for a typical Java application that pulls in a few Java SE or 3rd-party library classes.




            I would like to understand what gets added to metaspace after the first gc.




            I suspect that it is just an accounting thing; i.e. the amount of memory used by metaspace only gets updated when the GC runs. If you notice, the 2 apparent changes in metaspace usage (after the start of recording) both coincide with a GC event.






            share|improve this answer




























              0














              Metaspace is not "full". According to the captions, the limit for metaspace is 1.008G but you have 8.602M in there (out of a 9.125M initial allocation). That is about 1% of the limit.



              Metaspace contains things related to classes; i.e. bytecodes, compiled native code, descriptors, statics. ~8M bytes is quite a modest amount of metaspace for a typical Java application that pulls in a few Java SE or 3rd-party library classes.




              I would like to understand what gets added to metaspace after the first gc.




              I suspect that it is just an accounting thing; i.e. the amount of memory used by metaspace only gets updated when the GC runs. If you notice, the 2 apparent changes in metaspace usage (after the start of recording) both coincide with a GC event.






              share|improve this answer


























                0












                0








                0







                Metaspace is not "full". According to the captions, the limit for metaspace is 1.008G but you have 8.602M in there (out of a 9.125M initial allocation). That is about 1% of the limit.



                Metaspace contains things related to classes; i.e. bytecodes, compiled native code, descriptors, statics. ~8M bytes is quite a modest amount of metaspace for a typical Java application that pulls in a few Java SE or 3rd-party library classes.




                I would like to understand what gets added to metaspace after the first gc.




                I suspect that it is just an accounting thing; i.e. the amount of memory used by metaspace only gets updated when the GC runs. If you notice, the 2 apparent changes in metaspace usage (after the start of recording) both coincide with a GC event.






                share|improve this answer













                Metaspace is not "full". According to the captions, the limit for metaspace is 1.008G but you have 8.602M in there (out of a 9.125M initial allocation). That is about 1% of the limit.



                Metaspace contains things related to classes; i.e. bytecodes, compiled native code, descriptors, statics. ~8M bytes is quite a modest amount of metaspace for a typical Java application that pulls in a few Java SE or 3rd-party library classes.




                I would like to understand what gets added to metaspace after the first gc.




                I suspect that it is just an accounting thing; i.e. the amount of memory used by metaspace only gets updated when the GC runs. If you notice, the 2 apparent changes in metaspace usage (after the start of recording) both coincide with a GC event.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 24 '18 at 1:20









                Stephen CStephen C

                527k72588945




                527k72588945
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • 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%2fstackoverflow.com%2fquestions%2f53450931%2fjvm-metaspace-is-filled-after-minor-garbage-collection%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

                    "Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

                    Alcedinidae

                    RAC Tourist Trophy