Views: 3815
Last Modified: 22.09.2017

Attention! For operations, described in this lesson, *nix-systems administration knowledge is required. Prior to starting of operations, it is recommended to perform a full ┬źBitrix Virtual Appliance┬╗ backup.

To provide higher productivity of the file system, it is recommended to disable the timestamp modification when reading files and directories: noatime, nodiratime.

For this, parameters in the line with its UUID shall be edited (added into current line) in /etc/fstab:

UUID=abd9bdaa-e17d-40b3-aee5-37ef53a57b16 /    ext4    defaults,noatime,nodiratime    1 1
where UUID=abd9bdaa-e17d-40b3-aee5-37ef53a57b16 - unique disk identifier, which can be recognized in the console with blkid command.

Note: Instead of UUID, device name also can be used: /dev/sda1, /dev/sda2, /dev/sda3. Or volume label, if specified, for example: LABEL=root.

After restart, new settings will be applied.

To apply new settings without restarting the server, partitions can be remounted via the command:

mount -o remount,noatime,nodiratime /

Note: Creative approach should be applied to resolving the problem of file system productivity. If, for example, cache of some applications is still available on the disk, then the productivity can decrease as a result of proposed measures, because many applications clear cache via label-based index, which is recommended to be disabled in the example. In some cases, the commit time extension can give better result, especially if there is significant amount of available memory. Commit time is set by the commit parameter. To set it for 120 seconds, for example, it is necessary to add commit=120. That is, the set of options for mounting will be defaults,noatime,commit=120.

By default, data and metadata flush to disk happens each 5 sec. Delaying the flush time also can decrease file fragmentation on disk, if there are files available to which data are supplementary recorded. Logs files, for example.

Courses developed by Bitrix24