You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

kernel_task consumes a lot of RAM in early 2011 MBP, sometimes Finder too

Hi,

My old MBP3,1 (late 2007, 2.4 GHz Core 2 Duo) worked quite well with 4 GB of RAM, even after weeks without restarting. In fact, I used all available RAM only on some larger analyses using R, which loads the entire dataset in memory. To be able to run these few analyses faster on my new machine (early 2011 MBP), I bought the 8 GB RAM option.

In Activity Monitor, I noticed something strange. Whereas my old MBP shows kernel_taks as using between 100 and 200 MB of RAM, the new MBP uses about 550 MB just after the machine started up and often shows over 600 after a few hours or days of use. A one year old iMac, again Core 2 Duo with 4 GB of RAM, gives a kernel_task memory usage below 200 MB after weeks of use.

I've not been able to find what kernel_task does. Is this amount (around 600 MB, but it has gone up to 800) normal? Is it managiing the additional number of cores that requires this behind the scenes amount of RAM?

Anyway, I now quite often have more than 4 GB of RAM in use even when I have only a few applications running (not even including R!), which surprises me.

Also today, after moving a lot of files back and forth between an external drive and the new MBP, after emptying the garbage can that contained a hefty number of files and doing a first Time Machine backup, the Finder ended up using 2,4 GB of RAM according to Activity Monitor. I have never seen anything like this (although I admit not having Activity Monitor on all the time). Even after the backup was finished and the external drive disconnected (in fact the machine was left idling for a few hours) cpu usage was down to nearly zero, the Finder kept its 2.4 GB of RAM. I restarted and the new RAM usage for the Finder was 26 MB. I have a screen shot showing the 2.4 GB, but I could not find a way to attach it to this message. I can send it by email on request. I don't think this Finder behavior was normal.

Somewhat worried,

Denis

MacBook Pro 2.2 GHz i7, 8 GB RAM, Mac OS X (10.6.6)

Posted on Mar 16, 2011 12:04 AM

Reply
216 replies

Jul 28, 2011 9:31 PM in response to QuickTimeX

I have "resolved" the issue.


The key is that first of all, Intel integrated graphic cards uses 512MB RAM. Previous generation intel graphics may only use 128MB, or 265MB.


Secondly, you can boot into safe mode and compare what kexts are loaded, and then boot normally and see what's the additional stuff loaded.


When booted into Safe Mode, I see horrible graphic performance, suggesting the graphic cards are probably not really used. And in that mode, my kernel_task takes about <400MB RAM.


So 350 MB + 512 MB = almost 900MB RAM. Then I found a list of additional kext loaded. So those push the kernel_task to over 900MB.


I hope that resolves the problem. I wish I can turn off Intel integrated graphics. The ATi card in my MBP only has 256MB and is more powerful. There is no reason why Intel graphics needs 512MB.


Attached image shows the additional kexts loaded. Those include ATI and Intel kexts.


User uploaded file

Jul 28, 2011 9:41 PM in response to QuickTimeX

I don't think that's it. First off, I'm pretty sure the intel graphics only use 384 megs of ram. That doesn't account for 900 megs used by k_t. Second, the biggest kext loaded in normal boot mode is the ATI controller kext, which is only a few megs worth of RAM. That's why graphics were bad, it's because safe mode uses low-quality graphics drivers.

Jul 29, 2011 11:19 AM in response to DChabot

Yeah, I think that's the thing — that RAM stays reserved for the Intel GPU whether or not it's in use. I guess it's so there isn't an epic page in/out if a lot of your RAM is already in use by other applications when a switch to the HD 3000 occurs — I imagine that'd result in the switch appearing awfully sluggish, which isn't the seamless automatic switching experience Apple wants to promote. So I guess it's easier to keep a set amount of RAM for the integrated GPU, no matter what. It'd be nice if you could allocate the amount manually, though, and reduce it if you so desire. I wonder if there's a way to do this...?

Jul 29, 2011 11:40 AM in response to QuickTimeX

QuickTimeX


Strange you shoud be running out of RAM with 8GB. I always have 5.9 or 6GB free. Safari is a memory hog I agree that's why I don't use it. It seems nowadays all browsers are memory hogs Chrome, FF and Safari. I personally use FF 5.01. Safari runs and starts a process called webprocess which hogs RAM along with Safari. I also agree this kernel task is a problem, but it hasn't affected my system performance one bit. As I post this kernel task is using 692MB 82 threads and the CPU is only about 1.0%


I don't know what the solution is. But the people with only 4GB of RAM can easily upgrade to 8GB for as little as $44.00 as I just did. I bought 8GB of Corasir RAM from Amazon it was $54.00 and $44.00 after a $10.00 mail in rebate. The shipping is free from Amazon. Anyone can Google Corsair 8GB RAM upgrade and find the offer.


I haven't had any issues using the Corsair RAM.


Joseph

Jul 29, 2011 12:25 PM in response to wyager

With 4GB of RAM installed in my MBP 5,1 running 10.6.7, kernel task is using 178MB of RAM. FWIW, that's considerably less than the 256MB of RAM that is allocated to my integrated GPU — leading me to believe the GPU's RAM is not included in what the kernel task is reported to use.

kernel_task consumes a lot of RAM in early 2011 MBP, sometimes Finder too

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.