Why it can be busy
Spotlight keeps a local index so that Finder and Spotlight can find files, messages, photos, and other content quickly. Apple says indexing can occur after setup, a software update, or changes to data, and can take hours or days when there is a large amount of data. mds_stores is a system process associated with that indexing work. Its name alone does not explain why the workload is unusually high.
A restart, a macOS update, a large migration, a newly connected volume, or a large batch of changed files can therefore coincide with CPU use. CPU percentage alone does not tell you whether the work is harmful or when it will finish. Let a recent, explainable indexing run continue while the Mac is on power and otherwise idle.
- Open Spotlight with Command-Space and look for an indexing progress indicator.
- Note whether the activity began after an update, restore, drive connection, or large file change.
- Check free space and whether the Mac becomes responsive when the related work settles.
When to investigate
Follow up if activity remains high across several idle, powered sessions with no visible progress, search results are wrong, or one external disk reliably triggers the behavior. First install available macOS updates and inspect the disk or folder involved. Apple documents a supported way to reindex a troublesome disk or folder: add it temporarily in Spotlight Privacy, wait briefly, then remove it so macOS indexes it again.
Do not kill mds_stores or delete Spotlight databases as a first response. That can interrupt useful work and does not establish the cause. If the disk reports errors, is unexpectedly disconnecting, or the issue survives ordinary reindexing and updates, back up important data and seek Apple Support or qualified service.
Use WattGuard as evidence, not a repair tool
WattGuard shows this process family’s current CPU, wakeups and disk activity. Where macOS provides the data, it also shows current power and accumulated energy for the selected period. You can observe changes manually over time and compare them with the separate sleep analysis. Its sleep history can show whether completed sleep blockers overlap with a drain episode. It does not repair Spotlight, alter indexes, or prove that one daemon caused battery loss. Compare a later, normal idle session with the same Mac rather than treating a single reading as a verdict. For process monitoring in the Store edition, complete the setup wizard and install its companion files first; see the Energy Hogs feature page for setup.