Indices in a File Image¶
Since our math indexer creates a large amount of directories and files on disk. You are suggested to create a disk image as a loopback device to be partitioned by some file systems which do not put restriction on inodes. The file system should be efficient in crucial aspects of benchmarks that have great impact on search performance. Later, we can simply mount this disk image to be used as our index “disk”.
To create, mount and unmount a ReiserFS disk image, we provide a few simple
scripts located under
$PROJECT/indexer/scripts. Creating and mounting a
disk image just needs:
$ cd $PROJECT/indexer $ ./scripts/vdisk-creat.sh reiserfs $ sudo ./scripts/vdisk-mount.sh reiserfs
vdisk.img is created as our ReiserFS disk image, and is mounted to
./tmp so we can just use indexer and searcher on
./tmp like a
Remember to unmount after you finish using this image,
$ sudo ./scripts/vdisk-umount.sh
A few notes¶
1. Lacking kernel support for ReiserFS support¶
If you are running on kernel without ReiserFS support, modify scripts
argument above and change file system to
btrfs for similar performance.
For server distributions support ReiserFS, install
userland ReiserFS supports.
$ apt-get install reiserfsprogs
dd command reports exhausted memory¶
When you experience
dd command not being able to create certain size of image file:
dd: memory exhausted by input buffer of size 1073741824 bytes (1.0 GiB)
Try either reduce the
bs argument number of
dd, or use a disk swap file:
dd if=/dev/zero of=/swapspace bs=1M count=4000 mkswap /swapspace swapon /swapspace
3. TRIM in SSD¶
If you are doing indexing on an SSD drive (which is recommended because it is often more than 4 times faster than hard disk in terms of random write performance), it is highly suggested to enable SSD TRIM whenever it is supported, due to SSD Write Amplification (WA) effect. Without TRIM, the intensive writing onto SSD drive can cause very slow indexing performance and reduce SSD life span.
TRIM can be invoked either continuously by mounting your SSD drive with
sudo mount -o discard,noatime /dev/nvme0n1 ./mount‑point
noatime option stops to record the timestamp of accessing files (and directories) to further reduce the number of writing operations performed on SSD.
Or, by periodically run
$ sudo fstrim -v ./nvme0n1/
alternatively, the util‑linux package provides
fstrim.timer systemd unit files. Enabling the timer will activate the service weekly:
$ sudo systemctl enable fstrim.timer $ sudo systemctl start fstrim.timer $ journalctl ‑‑unit fstrim.timer # show logs
For cases when you have to mount an disk image created by another user (i.e., using a different uid), create a new user and log in as that user to access the mounted directory, instead of invoking
ls -l in mounted directory to see the uid/gid.
$ ls -l total 12 drwxrwxrwx 7 34549 34549 216 Apr 11 22:04 ./ ...
Create a user with uid = 34549:
$ sudo useradd arqmath3 -u 34549 -g 34549 -m -s /bin/bash $ ls -l total 12 drwxrwxrwx 7 arqmath3 arqmath3 216 Apr 11 22:04 ./ ...
Now, use the user
arqmath3 to access that directory.