Disk or partition in storage-engine device configuration

In our setup we have 2 disks that have been over provisioned and partitioned (4 partitions on each disk) according to https://www.aerospike.com/docs/operations/plan/ssd/ssd_setup.html#4

For the storage-engine device configuration https://www.aerospike.com/docs/reference/configuration/index.html#device

should we list all the partitions for each disk or only the disks?

device /dev/disk1part1
device /dev/disk1part2
device /dev/disk1part3
device /dev/disk1part4
device /dev/disk2part1
device /dev/disk2part2
device /dev/disk2part3
device /dev/disk2part4


device /dev/disk1
device /dev/disk2


if you want to use partitions, you want to list out all the partitions. most modern NVMe devices perform best with ~4 partitions, but ideally you want to ensure that the number of ‘devices’ does not exceed the number of CPU cores. how did you overprovision? are you sure your model of disk benefits from OP? a lot of disks dont. ideally you should test performance with ACT before/after overprovisioning to ensure you’re actually getting some gain.

We are using aws i3 instances with nvme devices. The number of partitions is equal to number of cores on the machine, so we end up with 8 partitions of 200GB each per device.

Did not benchmark overprovisioning, but aws does not OP their disks.

Do you have any documentation that mentions that device needs to be a partition instead of a disk? Thanks.

If you use the disk instead of a partition on the disk, Aerospike will happily overwrite the partition table on the disk :wink: .

Thanks for the confirmation!

We will change to use partitions instead of disks in the config.

