Library Indexer = Memory Hog on Pause
When I pause indexing, the Library indexer continues to use an incredible amount of memory. In fact, it seems to use the same as when it is actually indexing. What is it doing? What then is the benefit to pausing the indexing?
Comments
-
Well, it's not using the CPU while paused. I wouldn't really expect it lower it's memory usage if pause means "stop but maintain your current state until I tell you to continue".
MacBook Pro (2019), ThinkPad E540
0 -
When I pause indexing, the Library indexer continues to use an incredible amount of memory. In fact, it seems to use the same as when it is actually indexing. What is it doing? What then is the benefit to pausing the indexing?
How much memory do you have installed in your machine? What other applications are you running at the time? The memory will be reduced if other applications need it; if other applications don't need the memory, there's no point in freeing it right away (holding on to that memory doesn't really "hurt" any one).
0 -
I have a measly 1Gb. If the program does free up memory if needed, that's fine.
As the picture indicates above, I had that other notorious memory hog Firefox runing at the time, logos 3.0 updater, Google chrome with only 1 tab open, and my virus program running in the background.
I don't run a lot of programs at the same time, but I am concerned that the indexer will hog lots of memory especially if my library is going to be in an almost constant state of being reindexed!
0
