30GB out of 32GB being used for wired memory?
I have 32GB of memory and am downloading stuff over FTP using FileZilla. My memory usage is 31GB with 30GB of that being allocated for wired memory. Is this normal when downloading stuff over FTP?
UPDATE: after a bit more usage it looks like FileZilla was just a red herring. Kernel task is the one causing the ballooning Wired Mem usage. To be precise, here are the top three offenders and the wired memory usage.
1732608 com.nvidia.web.NVDAGP100HalWeb
6787072 com.nvidia.web.NVDAResmanWeb
8089600 com.apple.driver.AirPort.BrcmNIC
this was obtained by running
kextstat | awk 'NR==1{ printf "%10s %sn", $5, $6; } NR!=1{ printf "%10d %sn", $5, $6; }' | sort -n
which i found here: Why does leaked memory appear malloced to kernel_task, and why can't OS X therefore garbage collect it
here are latest screenshots from activity monitor.
why would the wifi driver be using up 8GB of wired memory? why would nvidia webdriver use up 7GB of wired memory?
macos memory virtual-memory
asked Jan 19 at 14:29
user25849user25849
1063
|
show 5 more comments
I have 32GB of memory and am downloading stuff over FTP using FileZilla. My memory usage is 31GB with 30GB of that being allocated for wired memory. Is this normal when downloading stuff over FTP?
UPDATE: after a bit more usage it looks like FileZilla was just a red herring. Kernel task is the one causing the ballooning Wired Mem usage. To be precise, here are the top three offenders and the wired memory usage.
1732608 com.nvidia.web.NVDAGP100HalWeb
6787072 com.nvidia.web.NVDAResmanWeb
8089600 com.apple.driver.AirPort.BrcmNIC
this was obtained by running
kextstat | awk 'NR==1{ printf "%10s %sn", $5, $6; } NR!=1{ printf "%10d %sn", $5, $6; }' | sort -n
which i found here: Why does leaked memory appear malloced to kernel_task, and why can't OS X therefore garbage collect it
here are latest screenshots from activity monitor.
why would the wifi driver be using up 8GB of wired memory? why would nvidia webdriver use up 7GB of wired memory?
macos memory virtual-memory
asked Jan 19 at 14:29
user25849user25849
1063
We might need to hop in Ask Different Chat to work out a couple things like where the GB are (you're only showing 2% of the storage) and if you log out and back in, without opening apps if the allocations change before you restart the OS.
– bmike♦
Jan 19 at 14:34
Memory pressure is green, and you're not swapping much out. If you're not seeing any slowdowns or beachballing, then MacOS is managing the memory well.
– benwiggy
Jan 19 at 15:04
Well said @benwiggy - and even if there is a slowdown or UI block, it’s not going to be memory ontention causing the issue.
– bmike♦
Jan 19 at 18:49
I'm no expert on MacOS internals, and didn't know what "wired memory" is until I googled it, but perhaps this is the same thing as the old linuxatemyram.com ?
– Thomas Padron-McCarthy
Jan 19 at 19:25
I disagree with @benwiggy. There is something wrong with 29GB in Wired memory. That is pages locked in RAM which stops macOS from managing virtual memory in the normal way. I have slowly increasing Wired memory and would like to know how to find out what is using it.
– Gilby
Jan 19 at 22:08
|
show 5 more comments
I have 32GB of memory and am downloading stuff over FTP using FileZilla. My memory usage is 31GB with 30GB of that being allocated for wired memory. Is this normal when downloading stuff over FTP?
UPDATE: after a bit more usage it looks like FileZilla was just a red herring. Kernel task is the one causing the ballooning Wired Mem usage. To be precise, here are the top three offenders and the wired memory usage.
1732608 com.nvidia.web.NVDAGP100HalWeb
6787072 com.nvidia.web.NVDAResmanWeb
8089600 com.apple.driver.AirPort.BrcmNIC
this was obtained by running
kextstat | awk 'NR==1{ printf "%10s %sn", $5, $6; } NR!=1{ printf "%10d %sn", $5, $6; }' | sort -n
which i found here: Why does leaked memory appear malloced to kernel_task, and why can't OS X therefore garbage collect it
here are latest screenshots from activity monitor.
why would the wifi driver be using up 8GB of wired memory? why would nvidia webdriver use up 7GB of wired memory?
macos memory virtual-memory
asked Jan 19 at 14:29
user25849user25849
1063
I have 32GB of memory and am downloading stuff over FTP using FileZilla. My memory usage is 31GB with 30GB of that being allocated for wired memory. Is this normal when downloading stuff over FTP?
UPDATE: after a bit more usage it looks like FileZilla was just a red herring. Kernel task is the one causing the ballooning Wired Mem usage. To be precise, here are the top three offenders and the wired memory usage.
1732608 com.nvidia.web.NVDAGP100HalWeb
6787072 com.nvidia.web.NVDAResmanWeb
8089600 com.apple.driver.AirPort.BrcmNIC
this was obtained by running
kextstat | awk 'NR==1{ printf "%10s %sn", $5, $6; } NR!=1{ printf "%10d %sn", $5, $6; }' | sort -n
which i found here: Why does leaked memory appear malloced to kernel_task, and why can't OS X therefore garbage collect it
here are latest screenshots from activity monitor.
why would the wifi driver be using up 8GB of wired memory? why would nvidia webdriver use up 7GB of wired memory?
macos memory virtual-memory
macos memory virtual-memory
asked Jan 19 at 14:29
user25849user25849
1063
asked Jan 19 at 14:29
user25849user25849
1063
edited 2 days ago
user25849
asked Jan 19 at 14:29
user25849user25849
1063
asked Jan 19 at 14:29
user25849user25849
1063
asked Jan 19 at 14:29
user25849user25849
1063
1063
We might need to hop in Ask Different Chat to work out a couple things like where the GB are (you're only showing 2% of the storage) and if you log out and back in, without opening apps if the allocations change before you restart the OS.
– bmike♦
Jan 19 at 14:34
Memory pressure is green, and you're not swapping much out. If you're not seeing any slowdowns or beachballing, then MacOS is managing the memory well.
– benwiggy
Jan 19 at 15:04
Well said @benwiggy - and even if there is a slowdown or UI block, it’s not going to be memory ontention causing the issue.
– bmike♦
Jan 19 at 18:49
I'm no expert on MacOS internals, and didn't know what "wired memory" is until I googled it, but perhaps this is the same thing as the old linuxatemyram.com ?
– Thomas Padron-McCarthy
Jan 19 at 19:25
I disagree with @benwiggy. There is something wrong with 29GB in Wired memory. That is pages locked in RAM which stops macOS from managing virtual memory in the normal way. I have slowly increasing Wired memory and would like to know how to find out what is using it.
– Gilby
Jan 19 at 22:08
|
show 5 more comments
We might need to hop in Ask Different Chat to work out a couple things like where the GB are (you're only showing 2% of the storage) and if you log out and back in, without opening apps if the allocations change before you restart the OS.
– bmike♦
Jan 19 at 14:34
Memory pressure is green, and you're not swapping much out. If you're not seeing any slowdowns or beachballing, then MacOS is managing the memory well.
– benwiggy
Jan 19 at 15:04
Well said @benwiggy - and even if there is a slowdown or UI block, it’s not going to be memory ontention causing the issue.
– bmike♦
Jan 19 at 18:49
I'm no expert on MacOS internals, and didn't know what "wired memory" is until I googled it, but perhaps this is the same thing as the old linuxatemyram.com ?
– Thomas Padron-McCarthy
Jan 19 at 19:25
I disagree with @benwiggy. There is something wrong with 29GB in Wired memory. That is pages locked in RAM which stops macOS from managing virtual memory in the normal way. I have slowly increasing Wired memory and would like to know how to find out what is using it.
– Gilby
Jan 19 at 22:08
We might need to hop in Ask Different Chat to work out a couple things like where the GB are (you're only showing 2% of the storage) and if you log out and back in, without opening apps if the allocations change before you restart the OS.
– bmike♦
Jan 19 at 14:34
We might need to hop in Ask Different Chat to work out a couple things like where the GB are (you're only showing 2% of the storage) and if you log out and back in, without opening apps if the allocations change before you restart the OS.
– bmike♦
Jan 19 at 14:34
Memory pressure is green, and you're not swapping much out. If you're not seeing any slowdowns or beachballing, then MacOS is managing the memory well.
– benwiggy
Jan 19 at 15:04
Memory pressure is green, and you're not swapping much out. If you're not seeing any slowdowns or beachballing, then MacOS is managing the memory well.
– benwiggy
Jan 19 at 15:04
Well said @benwiggy - and even if there is a slowdown or UI block, it’s not going to be memory ontention causing the issue.
– bmike♦
Jan 19 at 18:49
Well said @benwiggy - and even if there is a slowdown or UI block, it’s not going to be memory ontention causing the issue.
– bmike♦
Jan 19 at 18:49
I'm no expert on MacOS internals, and didn't know what "wired memory" is until I googled it, but perhaps this is the same thing as the old linuxatemyram.com ?
– Thomas Padron-McCarthy
Jan 19 at 19:25
I'm no expert on MacOS internals, and didn't know what "wired memory" is until I googled it, but perhaps this is the same thing as the old linuxatemyram.com ?
– Thomas Padron-McCarthy
Jan 19 at 19:25
I disagree with @benwiggy. There is something wrong with 29GB in Wired memory. That is pages locked in RAM which stops macOS from managing virtual memory in the normal way. I have slowly increasing Wired memory and would like to know how to find out what is using it.
– Gilby
Jan 19 at 22:08
I disagree with @benwiggy. There is something wrong with 29GB in Wired memory. That is pages locked in RAM which stops macOS from managing virtual memory in the normal way. I have slowly increasing Wired memory and would like to know how to find out what is using it.
– Gilby
Jan 19 at 22:08
|
show 5 more comments
1 Answer
1
active
oldest
votes
Most everything looks normal since the system reports it is able to fulfill all active memory requests (which is what green signifies), but we're not seeing the whole picture to understand the wired summary since your screen image doesn’t show all processes or wired allocations.
- The job of virtual memory is to keep everything loaded in RAM and only have just enough to satisfy a burst of requests. It will free up space only when needed, so large wired alone is no worry.
- You have no growth of swap space to speak of - so there's no runaway memory leak.
- The pressure graph is green so the system knows it can toss all sorts of cached memory and objects if a program needs more RAM and no requests are being slowed or denied.
- Wired isn't typically that high in my workloads, but more data is needed to know if that's causing any issues.
However, there are specific tools and a process to pin down exactly what process(es) have allocated wired memory as well as to watch real time the virtual memory statistics using vm_stat to validate my hunch / opinion (I don’t have enough data to be certain) that things are fine here.
In addition to my answer linked above - these threads are relevant for how wired memory used to work Lion and expecially 10.6 and older OS X. On the latest macOS, I’m not convinced excess wired is a problem anymore, but I’d love to help investigate if anyone can reproduce this case here with 90% or more of total memory being reported as Wired.
- What is wired memory?
- Why might more memory be wired in safe mode than in normal mode?
- Why does free + active + inactive + speculative + wired not equal total RAM?
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
1. The wired memory is fixed in RAM, so a bit hard to satisfy even a small burst of requests. 3. There is only 700MB of cached memory. Not much to be tossed out as required. 4. High wired will certainly cause issues (because it can't be paged out) if you try and run a memory hungry app.
– Gilby
Jan 19 at 22:13
@Gilby Thank you for the comments. I would love to see the results ofsysdiagnose FileZillaor whatever program / process that is using the most wired memory. In this question we’re lacking that level of detail. I bet one of us learns a lot, and I’m hoping it’s me. I can’t reproduce this scenario to validate my assumption that wired is being reported wrongly and there’s actually not a problem.
– bmike♦
Jan 19 at 22:19
Understanding what is using Wired has been bugging me for some time and I have not made much progress :( In the Activity Monitor screenshot, the numbers add up (App memory + Wired + Compressed + Cached = Physical). I will look further (but it won't be quick).
– Gilby
Jan 19 at 22:30
@Gilby Any time in the next 6 months is fine. I am patient and have been here writing about VM since 2012. Heck, remind me that I’ll bounty your question if you’re not happy with the answers it gets once it gets posted. Just be sure to get any sysdiagnose before you restart next time you catch this pattern, and get a second sysdiagnose after you reboot.
– bmike♦
Jan 19 at 22:32
i've found out that the nvidia web driver and airport are taking up the majority of the ballooning kernel_task allocation of wired memory. please see edit in original post
– user25849
2 days ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "118"
};
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f349037%2f30gb-out-of-32gb-being-used-for-wired-memory%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
Most everything looks normal since the system reports it is able to fulfill all active memory requests (which is what green signifies), but we're not seeing the whole picture to understand the wired summary since your screen image doesn’t show all processes or wired allocations.
- The job of virtual memory is to keep everything loaded in RAM and only have just enough to satisfy a burst of requests. It will free up space only when needed, so large wired alone is no worry.
- You have no growth of swap space to speak of - so there's no runaway memory leak.
- The pressure graph is green so the system knows it can toss all sorts of cached memory and objects if a program needs more RAM and no requests are being slowed or denied.
- Wired isn't typically that high in my workloads, but more data is needed to know if that's causing any issues.
However, there are specific tools and a process to pin down exactly what process(es) have allocated wired memory as well as to watch real time the virtual memory statistics using vm_stat to validate my hunch / opinion (I don’t have enough data to be certain) that things are fine here.
In addition to my answer linked above - these threads are relevant for how wired memory used to work Lion and expecially 10.6 and older OS X. On the latest macOS, I’m not convinced excess wired is a problem anymore, but I’d love to help investigate if anyone can reproduce this case here with 90% or more of total memory being reported as Wired.
- What is wired memory?
- Why might more memory be wired in safe mode than in normal mode?
- Why does free + active + inactive + speculative + wired not equal total RAM?
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
1. The wired memory is fixed in RAM, so a bit hard to satisfy even a small burst of requests. 3. There is only 700MB of cached memory. Not much to be tossed out as required. 4. High wired will certainly cause issues (because it can't be paged out) if you try and run a memory hungry app.
– Gilby
Jan 19 at 22:13
@Gilby Thank you for the comments. I would love to see the results ofsysdiagnose FileZillaor whatever program / process that is using the most wired memory. In this question we’re lacking that level of detail. I bet one of us learns a lot, and I’m hoping it’s me. I can’t reproduce this scenario to validate my assumption that wired is being reported wrongly and there’s actually not a problem.
– bmike♦
Jan 19 at 22:19
Understanding what is using Wired has been bugging me for some time and I have not made much progress :( In the Activity Monitor screenshot, the numbers add up (App memory + Wired + Compressed + Cached = Physical). I will look further (but it won't be quick).
– Gilby
Jan 19 at 22:30
@Gilby Any time in the next 6 months is fine. I am patient and have been here writing about VM since 2012. Heck, remind me that I’ll bounty your question if you’re not happy with the answers it gets once it gets posted. Just be sure to get any sysdiagnose before you restart next time you catch this pattern, and get a second sysdiagnose after you reboot.
– bmike♦
Jan 19 at 22:32
i've found out that the nvidia web driver and airport are taking up the majority of the ballooning kernel_task allocation of wired memory. please see edit in original post
– user25849
2 days ago
add a comment |
Most everything looks normal since the system reports it is able to fulfill all active memory requests (which is what green signifies), but we're not seeing the whole picture to understand the wired summary since your screen image doesn’t show all processes or wired allocations.
- The job of virtual memory is to keep everything loaded in RAM and only have just enough to satisfy a burst of requests. It will free up space only when needed, so large wired alone is no worry.
- You have no growth of swap space to speak of - so there's no runaway memory leak.
- The pressure graph is green so the system knows it can toss all sorts of cached memory and objects if a program needs more RAM and no requests are being slowed or denied.
- Wired isn't typically that high in my workloads, but more data is needed to know if that's causing any issues.
However, there are specific tools and a process to pin down exactly what process(es) have allocated wired memory as well as to watch real time the virtual memory statistics using vm_stat to validate my hunch / opinion (I don’t have enough data to be certain) that things are fine here.
In addition to my answer linked above - these threads are relevant for how wired memory used to work Lion and expecially 10.6 and older OS X. On the latest macOS, I’m not convinced excess wired is a problem anymore, but I’d love to help investigate if anyone can reproduce this case here with 90% or more of total memory being reported as Wired.
- What is wired memory?
- Why might more memory be wired in safe mode than in normal mode?
- Why does free + active + inactive + speculative + wired not equal total RAM?
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
1. The wired memory is fixed in RAM, so a bit hard to satisfy even a small burst of requests. 3. There is only 700MB of cached memory. Not much to be tossed out as required. 4. High wired will certainly cause issues (because it can't be paged out) if you try and run a memory hungry app.
– Gilby
Jan 19 at 22:13
@Gilby Thank you for the comments. I would love to see the results ofsysdiagnose FileZillaor whatever program / process that is using the most wired memory. In this question we’re lacking that level of detail. I bet one of us learns a lot, and I’m hoping it’s me. I can’t reproduce this scenario to validate my assumption that wired is being reported wrongly and there’s actually not a problem.
– bmike♦
Jan 19 at 22:19
Understanding what is using Wired has been bugging me for some time and I have not made much progress :( In the Activity Monitor screenshot, the numbers add up (App memory + Wired + Compressed + Cached = Physical). I will look further (but it won't be quick).
– Gilby
Jan 19 at 22:30
@Gilby Any time in the next 6 months is fine. I am patient and have been here writing about VM since 2012. Heck, remind me that I’ll bounty your question if you’re not happy with the answers it gets once it gets posted. Just be sure to get any sysdiagnose before you restart next time you catch this pattern, and get a second sysdiagnose after you reboot.
– bmike♦
Jan 19 at 22:32
i've found out that the nvidia web driver and airport are taking up the majority of the ballooning kernel_task allocation of wired memory. please see edit in original post
– user25849
2 days ago
add a comment |
Most everything looks normal since the system reports it is able to fulfill all active memory requests (which is what green signifies), but we're not seeing the whole picture to understand the wired summary since your screen image doesn’t show all processes or wired allocations.
- The job of virtual memory is to keep everything loaded in RAM and only have just enough to satisfy a burst of requests. It will free up space only when needed, so large wired alone is no worry.
- You have no growth of swap space to speak of - so there's no runaway memory leak.
- The pressure graph is green so the system knows it can toss all sorts of cached memory and objects if a program needs more RAM and no requests are being slowed or denied.
- Wired isn't typically that high in my workloads, but more data is needed to know if that's causing any issues.
However, there are specific tools and a process to pin down exactly what process(es) have allocated wired memory as well as to watch real time the virtual memory statistics using vm_stat to validate my hunch / opinion (I don’t have enough data to be certain) that things are fine here.
In addition to my answer linked above - these threads are relevant for how wired memory used to work Lion and expecially 10.6 and older OS X. On the latest macOS, I’m not convinced excess wired is a problem anymore, but I’d love to help investigate if anyone can reproduce this case here with 90% or more of total memory being reported as Wired.
- What is wired memory?
- Why might more memory be wired in safe mode than in normal mode?
- Why does free + active + inactive + speculative + wired not equal total RAM?
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
Most everything looks normal since the system reports it is able to fulfill all active memory requests (which is what green signifies), but we're not seeing the whole picture to understand the wired summary since your screen image doesn’t show all processes or wired allocations.
- The job of virtual memory is to keep everything loaded in RAM and only have just enough to satisfy a burst of requests. It will free up space only when needed, so large wired alone is no worry.
- You have no growth of swap space to speak of - so there's no runaway memory leak.
- The pressure graph is green so the system knows it can toss all sorts of cached memory and objects if a program needs more RAM and no requests are being slowed or denied.
- Wired isn't typically that high in my workloads, but more data is needed to know if that's causing any issues.
However, there are specific tools and a process to pin down exactly what process(es) have allocated wired memory as well as to watch real time the virtual memory statistics using vm_stat to validate my hunch / opinion (I don’t have enough data to be certain) that things are fine here.
In addition to my answer linked above - these threads are relevant for how wired memory used to work Lion and expecially 10.6 and older OS X. On the latest macOS, I’m not convinced excess wired is a problem anymore, but I’d love to help investigate if anyone can reproduce this case here with 90% or more of total memory being reported as Wired.
- What is wired memory?
- Why might more memory be wired in safe mode than in normal mode?
- Why does free + active + inactive + speculative + wired not equal total RAM?
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
edited Jan 19 at 22:30
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
answered Jan 19 at 14:44
bmike♦bmike
159k46285620
159k46285620
1. The wired memory is fixed in RAM, so a bit hard to satisfy even a small burst of requests. 3. There is only 700MB of cached memory. Not much to be tossed out as required. 4. High wired will certainly cause issues (because it can't be paged out) if you try and run a memory hungry app.
– Gilby
Jan 19 at 22:13
@Gilby Thank you for the comments. I would love to see the results ofsysdiagnose FileZillaor whatever program / process that is using the most wired memory. In this question we’re lacking that level of detail. I bet one of us learns a lot, and I’m hoping it’s me. I can’t reproduce this scenario to validate my assumption that wired is being reported wrongly and there’s actually not a problem.
– bmike♦
Jan 19 at 22:19
Understanding what is using Wired has been bugging me for some time and I have not made much progress :( In the Activity Monitor screenshot, the numbers add up (App memory + Wired + Compressed + Cached = Physical). I will look further (but it won't be quick).
– Gilby
Jan 19 at 22:30
@Gilby Any time in the next 6 months is fine. I am patient and have been here writing about VM since 2012. Heck, remind me that I’ll bounty your question if you’re not happy with the answers it gets once it gets posted. Just be sure to get any sysdiagnose before you restart next time you catch this pattern, and get a second sysdiagnose after you reboot.
– bmike♦
Jan 19 at 22:32
i've found out that the nvidia web driver and airport are taking up the majority of the ballooning kernel_task allocation of wired memory. please see edit in original post
– user25849
2 days ago
add a comment |
1. The wired memory is fixed in RAM, so a bit hard to satisfy even a small burst of requests. 3. There is only 700MB of cached memory. Not much to be tossed out as required. 4. High wired will certainly cause issues (because it can't be paged out) if you try and run a memory hungry app.
– Gilby
Jan 19 at 22:13
@Gilby Thank you for the comments. I would love to see the results ofsysdiagnose FileZillaor whatever program / process that is using the most wired memory. In this question we’re lacking that level of detail. I bet one of us learns a lot, and I’m hoping it’s me. I can’t reproduce this scenario to validate my assumption that wired is being reported wrongly and there’s actually not a problem.
– bmike♦
Jan 19 at 22:19
Understanding what is using Wired has been bugging me for some time and I have not made much progress :( In the Activity Monitor screenshot, the numbers add up (App memory + Wired + Compressed + Cached = Physical). I will look further (but it won't be quick).
– Gilby
Jan 19 at 22:30
@Gilby Any time in the next 6 months is fine. I am patient and have been here writing about VM since 2012. Heck, remind me that I’ll bounty your question if you’re not happy with the answers it gets once it gets posted. Just be sure to get any sysdiagnose before you restart next time you catch this pattern, and get a second sysdiagnose after you reboot.
– bmike♦
Jan 19 at 22:32
i've found out that the nvidia web driver and airport are taking up the majority of the ballooning kernel_task allocation of wired memory. please see edit in original post
– user25849
2 days ago
1. The wired memory is fixed in RAM, so a bit hard to satisfy even a small burst of requests. 3. There is only 700MB of cached memory. Not much to be tossed out as required. 4. High wired will certainly cause issues (because it can't be paged out) if you try and run a memory hungry app.
– Gilby
Jan 19 at 22:13
1. The wired memory is fixed in RAM, so a bit hard to satisfy even a small burst of requests. 3. There is only 700MB of cached memory. Not much to be tossed out as required. 4. High wired will certainly cause issues (because it can't be paged out) if you try and run a memory hungry app.
– Gilby
Jan 19 at 22:13
@Gilby Thank you for the comments. I would love to see the results of
sysdiagnose FileZilla or whatever program / process that is using the most wired memory. In this question we’re lacking that level of detail. I bet one of us learns a lot, and I’m hoping it’s me. I can’t reproduce this scenario to validate my assumption that wired is being reported wrongly and there’s actually not a problem.– bmike♦
Jan 19 at 22:19
@Gilby Thank you for the comments. I would love to see the results of
sysdiagnose FileZilla or whatever program / process that is using the most wired memory. In this question we’re lacking that level of detail. I bet one of us learns a lot, and I’m hoping it’s me. I can’t reproduce this scenario to validate my assumption that wired is being reported wrongly and there’s actually not a problem.– bmike♦
Jan 19 at 22:19
Understanding what is using Wired has been bugging me for some time and I have not made much progress :( In the Activity Monitor screenshot, the numbers add up (App memory + Wired + Compressed + Cached = Physical). I will look further (but it won't be quick).
– Gilby
Jan 19 at 22:30
Understanding what is using Wired has been bugging me for some time and I have not made much progress :( In the Activity Monitor screenshot, the numbers add up (App memory + Wired + Compressed + Cached = Physical). I will look further (but it won't be quick).
– Gilby
Jan 19 at 22:30
@Gilby Any time in the next 6 months is fine. I am patient and have been here writing about VM since 2012. Heck, remind me that I’ll bounty your question if you’re not happy with the answers it gets once it gets posted. Just be sure to get any sysdiagnose before you restart next time you catch this pattern, and get a second sysdiagnose after you reboot.
– bmike♦
Jan 19 at 22:32
@Gilby Any time in the next 6 months is fine. I am patient and have been here writing about VM since 2012. Heck, remind me that I’ll bounty your question if you’re not happy with the answers it gets once it gets posted. Just be sure to get any sysdiagnose before you restart next time you catch this pattern, and get a second sysdiagnose after you reboot.
– bmike♦
Jan 19 at 22:32
i've found out that the nvidia web driver and airport are taking up the majority of the ballooning kernel_task allocation of wired memory. please see edit in original post
– user25849
2 days ago
i've found out that the nvidia web driver and airport are taking up the majority of the ballooning kernel_task allocation of wired memory. please see edit in original post
– user25849
2 days ago
add a comment |
Thanks for contributing an answer to Ask Different!
- 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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f349037%2f30gb-out-of-32gb-being-used-for-wired-memory%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
We might need to hop in Ask Different Chat to work out a couple things like where the GB are (you're only showing 2% of the storage) and if you log out and back in, without opening apps if the allocations change before you restart the OS.
– bmike♦
Jan 19 at 14:34
Memory pressure is green, and you're not swapping much out. If you're not seeing any slowdowns or beachballing, then MacOS is managing the memory well.
– benwiggy
Jan 19 at 15:04
Well said @benwiggy - and even if there is a slowdown or UI block, it’s not going to be memory ontention causing the issue.
– bmike♦
Jan 19 at 18:49
I'm no expert on MacOS internals, and didn't know what "wired memory" is until I googled it, but perhaps this is the same thing as the old linuxatemyram.com ?
– Thomas Padron-McCarthy
Jan 19 at 19:25
I disagree with @benwiggy. There is something wrong with 29GB in Wired memory. That is pages locked in RAM which stops macOS from managing virtual memory in the normal way. I have slowly increasing Wired memory and would like to know how to find out what is using it.
– Gilby
Jan 19 at 22:08