One of linux performance tuning: Disk partitioning policy

One of linux performance tuning: Disk partitioning policies for servers, whether in windows or linux, affect system performance. the disk partition is then formatted into a certain format of system file, and finally stored in user or system data. If the partition where the data is located is easy to read, the response will be... one of linux performance tuning: Disk partitioning policies for servers, whether in windows or linux, affect system performance. after partitioning a disk, it is formatted as a system file in a certain format. Finally, it is stored in user or system data. the faster the response speed when data is easily read in the partition where the data is located. of course, there are also the opposite situations. before "data hunger" occurs, we must first understand some features of the disk (physical factors that affect I/O ): 1> storage density (the higher the storage density depends on the external channel), (the same speed, the more data is read from the external channel) ----- storage user data partition: partition sector formatting within a certain range on the disk: based on the partition, identify the partition speed of each sector> formatting speed Note: The lower the partition number, the more external 2> Total The line speed is much lower than the kernel processing time. 3> when looking at a disk structure diagram (at the time when different channels are switched), you should first understand that "the sectors are counted from the periphery ", for details, refer to some information on the internet. the default partitions start from the periphery, but we must combine the physical attributes of the disk with our own requirements to divide the partitions. Principle: the more frequently accessed data is stored on the outermost side of the disk. Implementation 1: When rhel6.0 is installed, you cannot specify the start sector number. you can only partition the partition before you can partition partitions that store frequent access, and the rest will be used by the system. Note: implementation of data with low partition numbers for frequent access 2: Do not manually calculate the number of cylinders and specify the start position (in this case, make a record) the following are some suggestions for a cylindrical cylinder about 7 M: 1. /, swap,/var,/home,/usr, the commonly used partition must first use a separate partition 2. the first partition is swap ------ used to optimize the memory swap operation 3. for example,/data is frequently accessed user data, which can be used as the second partition 4. the logs are/var/------ in sequence, and the/usr/------ system library file is 5. //, some configuration files in the/boot dependency are rarely read, and some files in the/boot partition are also the same. of course, it would be better to have multiple disks, data can be directly stored on a disk with good performance. RAID can also be used to speed up access.