How to get the best performance of a Samba file server in a Proxmox hypervisor environment?

Question

System administration

Proxmox is on mdadm raid1 with two 4TB disks.
Two storages are configured:
local - directory (100GB for images and backups)
data - LVM (everything else for raw VM and LXC disks)

What is the best way to implement a Samba file server on it with access to a domain with AD for maximum performance?
I see three options:

1. Classic VM with a raw disk in data and a writeback setting on it
   
2. Samba in LXC container with raw disk in data
   
3. The same container, but remounted without disk quotas in local
   

The last option is the most interesting. By default, the performance of the disk subsystem in LXC for some reason is almost two times less than on the hypervisor host. But if you do so

vzdump 100 -compress lzo -dumpdir /var/lib/vz/dump -mode snapshot -remove 0
pct restore 200 /var/lib/vz/dump/vzdump-lxc-200-2020_05_06-02_35_29.tar.lzo --rootfs local:0

then the restored container without disk quotas in local is already almost equal in performance to the host. The problem of controlling the place in local is solved by monitoring in zabbix. You will have to change storages, make local larger, and smaller data in lvm for the remaining VMs that cannot be put into LXC.

But first I would like to know who has experience in such a transfer, what pitfalls can surface on Samba connected to a domain with AD?
Or maybe there are other options that I haven't considered?

Answer 1

Your question is not very clear, you have already done all the tests and got the same results as everyone else.
Yes, in the case of a hack, it will be better when restoring, since the files are directly in the host's fs and all security and space concerns are yours.

Answer 2

They have a hacked LXC. Maybe because of this. Put on VM in raw directsync format.