I've had runaway mds processes before that caused no end of problems, not only using lots of RAM but also using lots of CPU. The conflict turned out to be CrashPlan on one occasion and on another a problematic file that mds was just spinning on and getting nowhere with.
On Tue, Mar 6, 2012 at 8:49 PM, LuKreme <[email protected]> wrote: > > On 06 Mar 2012, at 13:28 , Michael Winter wrote: > >> >> On Mar 6, 2012, at 9:35 AM, LuKreme wrote: >> >>> >>> My mds process is using 500MB of RAM (Real Mem) which seems a bit excessive >>> to me. >> >> Isn't that a good thing? As long as the memory isn't needed for anything >> else, it makes sense to keep as much information as possible in memory in >> case its needed. Otherwise the memory is just sitting there doing nothing. > > It is concerning to me that the mds process *ever* needs that much memory. I > mean, I know what mds does, and it shouldn't need a whole lot of RAM to do > it, I don't think. On the mini, it uses about 130MB of Real memory, which > seems more reasonable. Its shared memory is only 26MB, so why's it need over > 500MB (it's grown)? That's twice what the Finder or Safari use, more than > Safari+Safari Web content or iTunes, and just barely less than the mysterious > kernel_task. > > Also, its VM keeps growing (up to 3.77GB right now), though I don't care > about that. > > -- > Hard work pays off in the future. Laziness pays off now. > > _______________________________________________ > MacOSX-talk mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-talk _______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
