Locate the system folder.

2.

I checked here, and the system disk is less than 10G.

3.

Right-click a blank area to see display options.

4.

Set the arrangement to size.

5.

By setting it in each root directory, you can find out what the largest file is.

6.

Next, download a software cleaning software uninstall, here is DR.Cleaner

7.

You can also optimize the system, clean up garbage and cache.

Clean up the Mac system, which takes up a lot of space and lacks space. Check the file size distribution of the system.

Background:

Recently, there is not enough space for the old reminder, which is embarrassing. I've been playing system prompts.

As shown in the figure, there are only a few G's left in the space of 256, and the system with the largest head occupies 160G, accounting for more than 60%.

Under normal circumstances; We can click "Manage" to enter the system disk optimization interface;

This is suitable for simple file occupancy analysis. Generally, we can solve the problem of insufficient space by cleaning up manuscripts and recycling bins.

1. Empty the recycle bin.

2. In the manuscript, sort by file size and delete unnecessary files.

3. For GarageBand, this is an analog instrument on the system and is generally not used.

Cleaning method:

RM-RF/ Library/Application \ Support /GarageBand

RM-RF/ Library/Application \ Support/Logic

RM-RF/ library /Audio/Apple\ Loops

However, for the culprit, the system's 160G, how can we know her internal storage distribution?

Text:

Details on how to view the file usage of the system.

First, open the terminal and enter.

du -sh *

This command is used to view the size distribution of all files in the root directory, as shown in the figure:

Among them, we can easily see the size ratio of each file and quickly locate the file with the largest ratio: the library.

Second, enter a command to enter the library file path.

CD ~/ library

Then, look at all the file size distributions under the library.

Input:

du -d 1 -h

We can easily find the largest file: //Developer.

Of course, we can also see other file sizes at a glance.

Third, you can basically know the following routines here, and you can continue to look down.

For example, I continue to enter the Developer file here, and then check the size of each of his subfiles:

Basically, you can know the general reason by looking at two or three floors. Because my place is Cheng, Xcode is the root cause, accounting for half of the system size 160G.

At this point, if you are also Cheng, you can continue to watch if you are interested. If you are not interested, you can skip to step 4 directly.

This is basically the end, and the approximate space occupation distribution is basically known from the above picture.

The above is about how to view and analyze files. If you are an iOS programmer, there are several cleaning steps (cleaning Xcode cache).

After testing, I temporarily found that these files can be cleaned normally:

1 ./Archives This file stores all historical packaging files. You can delete some history packages. If you don't trust, you can keep the latest ones, but it's okay to delete them all. However, if you delete them, we can't see anything in the Xcode packaging and uploading interface (as shown in the figure below, the things in this interface are gone).

2. You should be familiar with file/derived data, which stores some cached data of all projects, including compiled cached files. This file can be completely erased. Of course, you can also keep some recent projects and clean up the cache of historical projects for the time being.

3 ./iOS DeviceSupport This file stores xcode's support files for various versions of mobile phones. If your project no longer needs to support iOS6 and iOS7, you can clear the supporting files based on iOS6 and iOS7 first.

Attached is the complete version of Xcode's slimming method, and those who are interested can operate according to this article.

Fourthly, through the layer-by-layer analysis in the third step, you can basically know the size distribution of each file, and you can also find some unnecessary junk files, most of which are cache files. You can clean them up properly ~

Finally, if there are people who are not interested in the command, they can also view it intuitively through the Finder.

Open Spotlight(Command+ space or Ctrl+ space) and type ~/Library.

The file path that can enter the resource pool.

The rightmost file corresponds to the file just ordered. We can find the most occupied files according to the command, click here to view them, and then clean them up properly according to our own needs.

For example, the path I finally analyzed above:

Special update:

The cleanliness of this article may not be particularly comprehensive. For example, commonly used QQ and WeChat software actually take up a lot of space (10~20G ~ 20g).