Regarding DDBB performance, I/O and SSD disks

[dragonauta]

Hi all
I would like to virtualize a physical Linux Server with a Firebird database into proxmox
I know that DDBB usually needs lots of I/O.

So I thought I should have a SSD drive to put the DDBB (because the performance)

I think I have to options:
1. use KVM, create a filesystem onto SSD drive and add partition to VM using virtio driver
2. use containers and bind-mount the device into container

Which would be better?
Any advice would be really appreciated
Thanks

 

[udo]

Hi all
I would like to virtualize a physical Linux Server with a Firebird database into proxmox
I know that DDBB usually needs lots of I/O.

So I thought I should have a SSD drive to put the DDBB (because the performance)

I think I have to options:
1. use KVM, create a filesystem onto SSD drive and add partition to VM using virtio driver
2. use containers and bind-mount the device into container

Which would be better?
Any advice would be really appreciated
Thanks

Hi,
for IO the OpenVZ + bind-mount is the best option. For Live-Migration (if you have shared storage like DRBD ob SSDs (ok, I know, that DRBD isn't real shared storage)) is KVM much better...
Due safety, I choose normaly kvm is this case... but this depends on your setup and needs.

Udo

 

[dragonauta]

thanks Udo.
I will try to explain better.

It will be a really small-non-critical installation, into an i7 with 16GB Ram and SATA3 RAID1

Will be running a three layer ERP: client layer running on clients PC's, transaction layer on a Windows Server, and DDBB layer on a debian+firebird ddbb.
It's not a critical application... could be down for a day, not a big problem.
That's why we're not implementing migration, HA nor cluster.

We were considering two virtual machines: one KVM for Windows Server (transactions server) and one CT for DDBB

In worst case, we would reinstall proxmox, import both virtual machines and restore DDBB backup.

In this case, and based on your response, I would go for OpenVZ+bind-mount.
SATA3 RAID would be for system, and a single SSD only for database.

What about OpenVZ snapshots? could be done when using bind-mount? (logic says me "you can't")
thanks

 

[mir]

Using RAID1 as storage for a database is asking for trouble. 4-8K random writes are the typical usecase for a database and RAID1 will kill your IO. You should carefully consider going for RAID10 for a database storage.

 

[dragonauta]

Thanks mir.
Maybe I didn't express well.
Sata RAID1 will be for system: proxmox SO and local storage
A single SSD will be bind-mounted only for DDBB.

I plan a CT stored on local storage (Raid1 on Sata) and a SSD bind-mounted for DDBB

Enviado desde mi GT-I8190L mediante Tapatalk