Then move on to helping other people.
Hope Apple reads these forums and sees just how many people are having problems with their lovely OS needing 4GB of RAM to do its tasks. This makes it more of a resource hog than even Vista. If we get 16GB of RAM or even 1TB of RAM if it existed, the lovely OS will take 500GB of it. I'm sure this makes sense to you and allows you to maintain your super gracious manner.
Thanks wyager. After a fresh boot, it's about 600MB. The 4GB is what it's running now. I booted last evening my time.
Based on some suggestions on these forums i downloaded "gfcardstatus" and let it run. Without it, the whole system was crashing (that gray screen with white text -- similar to windows blue screen -- that takes over and says please reboot), but at least it's not crashing now, but the overall experience is sluggish and the mouse cursor just hangs sometimes because it's so slow.
Because of my industry, I have to work with large video files. I wonder if the deleting/adding/deleting of lage video files (over 6GB or so each file) has defragmented my system? Or what? Why's it taking so much for the kernel_task?
Many thanks for any ideas..
Got 16 GB of RAM and kernel_task jumped to 1.29 GB in a few hours... I wonder what did Apple do to make iPads run with half a gig... will try booting in 32 bit even if it takes a little bit more
Hi Guys - Newbie here. Recently switched from Quad core PC (4years old) 4G of RAM to a MBP i7 8G
Using Photoshop CS5, Lightroom, with half a dozen passive tabs open on Firefox, Itunes blasting out and..... nothing else. I'm often left with a DOZEN OR SO MEGS OF RAM!!!
Now, twenty years ago I'd be really happy with this but I'm now rather bored of that spinning wheel of death.
In truth - My Mac has been pretty stable but not much faster than my old PC. I expected more.
Paid £35 for an Apple support call (Yet I'm still in warranty)
Paid £35 petrol for a trip to Genius store in Manchester. The man smiled at me and said my Apple is perfect - It's obviously a software issue.
So guys.... It's a software issue. The MacPro seems to not like CS5 or Lightroom, or maybe even I-Tunes, or Firefox. (I've re-installed everything and followed Adobes best practices to the letter. Apart from putting my scratch discs on a seperate partition) - What does it like? Can it cope with word documents or spreadsheets?
Since returning from Genius, I've tried running aplications without CS5 and Lightroom. OK, now I have a whopping 3G of RAM left. Any idea why 5G of RAM is being eaten up by basic stuff?
If I'd have waited a few more weeks I could have bought a MBP with 16G of RAM. Sadly I'm maxed out at 8.
Apple support isn't helping. Honestly have no idea why Apple supporters are so loyal to the brand. (It looks dead sexy though)
for your info...
i7, 8G RAM
only Firefox open with this tab
Kernal_task is holding steady at 882Megs
I'm flying! - Er, unless I actually want to do something...
So after around half an hour of activity. You'll see from the grabshot...
I've been working on one layered file. (Admittedly a large one with 20 layers)
Closed the file down.
Now cs5, Lightroom Firefox and Finder running.
1.57G free now. (used more than 6G RAM)
It seems that CS5 is hogging 2.3 G of RAM, even though the file was closed over ten minutes ago.
Anyone know why this memory stays Used even when programmes are idle? This normal?
Dave1click: I don't know whether you've seen the article linked below:
It certainly won't answer all your questions, but it's a useful starting point for understanding memory usage, allocation and reporting in OS X. What you know from using Windows is not all applicable to the Mac.
Dave, we feel your pain. However, you might be able to palliate the problem with photoshop memory usage.
There are several probable reasons that CS5 is using so much RAM, ranging from a problem on Adobe's end to a problem with the OS (which is certainly the case with Kernel_task).
I recommend installing the developer tools, and then running the "purge" command in the terminal. This command tells the kernel to dump all inactive memory, and might perform some garbage collection functions as well. I'm not really sure, because the man page is outdated, but the function works.
Objective-C (the language used to make most OS X applications) is not garbage-collected, and has weird memory management, so a lot of applications end up accidentally "using" a huge chunk of memory that they're not actually using. It's a little hard to explain, but if you're programming-oriented, you should be able to google search for more info.