Windows server 2012 R2 - Memory in use is more than commit charge












1















One of our Windows server reported 100% memory usage and please see the attached image for details.



What I don't understand is that "In use (31.5G)" is more than "commit charge(6.6G)", does that mean something is wrong or because some memory in use is not pageable?



enter image description here










share|improve this question























  • In this context I think "In use" is referring to total physical RAM being used, whereas "committed", refers to the virtual address space commit charge / commit charge limit. So no, I wouldn't say something is wrong, you're just running out of RAM

    – BrianC
    Mar 23 '16 at 2:01








  • 1





    If possible download RamMap from microsoft and post a image of the "Use Counts" tab.

    – Scott Chamberlain
    Mar 23 '16 at 3:57













  • @ScottChamberlain that helped, there are 28G of mapped files. I am still surprised that resource monitor does not show it at all. Anyway thanks for the information.

    – Ask and Learn
    Mar 23 '16 at 5:06
















1















One of our Windows server reported 100% memory usage and please see the attached image for details.



What I don't understand is that "In use (31.5G)" is more than "commit charge(6.6G)", does that mean something is wrong or because some memory in use is not pageable?



enter image description here










share|improve this question























  • In this context I think "In use" is referring to total physical RAM being used, whereas "committed", refers to the virtual address space commit charge / commit charge limit. So no, I wouldn't say something is wrong, you're just running out of RAM

    – BrianC
    Mar 23 '16 at 2:01








  • 1





    If possible download RamMap from microsoft and post a image of the "Use Counts" tab.

    – Scott Chamberlain
    Mar 23 '16 at 3:57













  • @ScottChamberlain that helped, there are 28G of mapped files. I am still surprised that resource monitor does not show it at all. Anyway thanks for the information.

    – Ask and Learn
    Mar 23 '16 at 5:06














1












1








1








One of our Windows server reported 100% memory usage and please see the attached image for details.



What I don't understand is that "In use (31.5G)" is more than "commit charge(6.6G)", does that mean something is wrong or because some memory in use is not pageable?



enter image description here










share|improve this question














One of our Windows server reported 100% memory usage and please see the attached image for details.



What I don't understand is that "In use (31.5G)" is more than "commit charge(6.6G)", does that mean something is wrong or because some memory in use is not pageable?



enter image description here







windows memory






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 23 '16 at 1:10









Ask and LearnAsk and Learn

19328




19328













  • In this context I think "In use" is referring to total physical RAM being used, whereas "committed", refers to the virtual address space commit charge / commit charge limit. So no, I wouldn't say something is wrong, you're just running out of RAM

    – BrianC
    Mar 23 '16 at 2:01








  • 1





    If possible download RamMap from microsoft and post a image of the "Use Counts" tab.

    – Scott Chamberlain
    Mar 23 '16 at 3:57













  • @ScottChamberlain that helped, there are 28G of mapped files. I am still surprised that resource monitor does not show it at all. Anyway thanks for the information.

    – Ask and Learn
    Mar 23 '16 at 5:06



















  • In this context I think "In use" is referring to total physical RAM being used, whereas "committed", refers to the virtual address space commit charge / commit charge limit. So no, I wouldn't say something is wrong, you're just running out of RAM

    – BrianC
    Mar 23 '16 at 2:01








  • 1





    If possible download RamMap from microsoft and post a image of the "Use Counts" tab.

    – Scott Chamberlain
    Mar 23 '16 at 3:57













  • @ScottChamberlain that helped, there are 28G of mapped files. I am still surprised that resource monitor does not show it at all. Anyway thanks for the information.

    – Ask and Learn
    Mar 23 '16 at 5:06

















In this context I think "In use" is referring to total physical RAM being used, whereas "committed", refers to the virtual address space commit charge / commit charge limit. So no, I wouldn't say something is wrong, you're just running out of RAM

– BrianC
Mar 23 '16 at 2:01







In this context I think "In use" is referring to total physical RAM being used, whereas "committed", refers to the virtual address space commit charge / commit charge limit. So no, I wouldn't say something is wrong, you're just running out of RAM

– BrianC
Mar 23 '16 at 2:01






1




1





If possible download RamMap from microsoft and post a image of the "Use Counts" tab.

– Scott Chamberlain
Mar 23 '16 at 3:57







If possible download RamMap from microsoft and post a image of the "Use Counts" tab.

– Scott Chamberlain
Mar 23 '16 at 3:57















@ScottChamberlain that helped, there are 28G of mapped files. I am still surprised that resource monitor does not show it at all. Anyway thanks for the information.

– Ask and Learn
Mar 23 '16 at 5:06





@ScottChamberlain that helped, there are 28G of mapped files. I am still surprised that resource monitor does not show it at all. Anyway thanks for the information.

– Ask and Learn
Mar 23 '16 at 5:06










1 Answer
1






active

oldest

votes


















0














"Commit charge" is the sum of the virtual address space allocated privately to all processes, plus some system-wide allocations like the nonpaged pool. The system-wide limit on commit charge is given by the sum of RAM + pagefile space; however, a given "commit charge" does not necessarily mean that all of that space is actually in use, either in RAM or in the pagefile. Thus the "commit charge" can greatly exceed the actual RAM that it's using (even if you don't have a pagefile).



But there are many other things that use RAM. "In use" is the total of all processes' use of RAM (of which the in-memory subset of each process's commit charge is only part; most of the remainder is typically file mappings), plus all of the system-wide usage.



So it is not at all unexpected for commit charge to be much smaller than the RAM "in use". It isn't really supposed to be the same. For that matter it's also possible for commit charge to be larger than the RAM "in use" (if a lot of committed memory has been allocated but not yet referenced, hence not "faulted in", i.e. realized in RAM).






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    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%2fsuperuser.com%2fquestions%2f1056220%2fwindows-server-2012-r2-memory-in-use-is-more-than-commit-charge%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














    "Commit charge" is the sum of the virtual address space allocated privately to all processes, plus some system-wide allocations like the nonpaged pool. The system-wide limit on commit charge is given by the sum of RAM + pagefile space; however, a given "commit charge" does not necessarily mean that all of that space is actually in use, either in RAM or in the pagefile. Thus the "commit charge" can greatly exceed the actual RAM that it's using (even if you don't have a pagefile).



    But there are many other things that use RAM. "In use" is the total of all processes' use of RAM (of which the in-memory subset of each process's commit charge is only part; most of the remainder is typically file mappings), plus all of the system-wide usage.



    So it is not at all unexpected for commit charge to be much smaller than the RAM "in use". It isn't really supposed to be the same. For that matter it's also possible for commit charge to be larger than the RAM "in use" (if a lot of committed memory has been allocated but not yet referenced, hence not "faulted in", i.e. realized in RAM).






    share|improve this answer




























      0














      "Commit charge" is the sum of the virtual address space allocated privately to all processes, plus some system-wide allocations like the nonpaged pool. The system-wide limit on commit charge is given by the sum of RAM + pagefile space; however, a given "commit charge" does not necessarily mean that all of that space is actually in use, either in RAM or in the pagefile. Thus the "commit charge" can greatly exceed the actual RAM that it's using (even if you don't have a pagefile).



      But there are many other things that use RAM. "In use" is the total of all processes' use of RAM (of which the in-memory subset of each process's commit charge is only part; most of the remainder is typically file mappings), plus all of the system-wide usage.



      So it is not at all unexpected for commit charge to be much smaller than the RAM "in use". It isn't really supposed to be the same. For that matter it's also possible for commit charge to be larger than the RAM "in use" (if a lot of committed memory has been allocated but not yet referenced, hence not "faulted in", i.e. realized in RAM).






      share|improve this answer


























        0












        0








        0







        "Commit charge" is the sum of the virtual address space allocated privately to all processes, plus some system-wide allocations like the nonpaged pool. The system-wide limit on commit charge is given by the sum of RAM + pagefile space; however, a given "commit charge" does not necessarily mean that all of that space is actually in use, either in RAM or in the pagefile. Thus the "commit charge" can greatly exceed the actual RAM that it's using (even if you don't have a pagefile).



        But there are many other things that use RAM. "In use" is the total of all processes' use of RAM (of which the in-memory subset of each process's commit charge is only part; most of the remainder is typically file mappings), plus all of the system-wide usage.



        So it is not at all unexpected for commit charge to be much smaller than the RAM "in use". It isn't really supposed to be the same. For that matter it's also possible for commit charge to be larger than the RAM "in use" (if a lot of committed memory has been allocated but not yet referenced, hence not "faulted in", i.e. realized in RAM).






        share|improve this answer













        "Commit charge" is the sum of the virtual address space allocated privately to all processes, plus some system-wide allocations like the nonpaged pool. The system-wide limit on commit charge is given by the sum of RAM + pagefile space; however, a given "commit charge" does not necessarily mean that all of that space is actually in use, either in RAM or in the pagefile. Thus the "commit charge" can greatly exceed the actual RAM that it's using (even if you don't have a pagefile).



        But there are many other things that use RAM. "In use" is the total of all processes' use of RAM (of which the in-memory subset of each process's commit charge is only part; most of the remainder is typically file mappings), plus all of the system-wide usage.



        So it is not at all unexpected for commit charge to be much smaller than the RAM "in use". It isn't really supposed to be the same. For that matter it's also possible for commit charge to be larger than the RAM "in use" (if a lot of committed memory has been allocated but not yet referenced, hence not "faulted in", i.e. realized in RAM).







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Mar 23 '16 at 11:10









        Jamie HanrahanJamie Hanrahan

        18.9k34280




        18.9k34280






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • 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%2fsuperuser.com%2fquestions%2f1056220%2fwindows-server-2012-r2-memory-in-use-is-more-than-commit-charge%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

            Plaza Victoria

            Puebla de Zaragoza

            Musa