How would it affect performance of the whole lvm2 pool if different physical volumes have had different speed properties?
I'm speaking foremost in the AWS/EC2 context. If I have one physical volume which is 1TB (3000 IOps), the other is 100GB (300 IOps), would it degrade the whole LVM volume group to just 300 IOps?
Based on this answer it seems that LVM is:
really just a table lookup in a fairly small table that block X is actually block Y on device Z.
Hence if I write one bunch of small files, which just happen to be mapped to the speedier physical volume, the whole transaction must be quicker than if that it was mapped to the slower drive?
How does it work in general?
lvmcacheas this may lead to reconsidering a cheaper backing space storage, but I'm pretty sure that random access time with the large volumes of data an enormous number of files will be crap. In my case performance will be (kind of) predictable either way, as I have continuously growing data, hence with 900 GB and 100 GBPVsonly 10% of the latest files will be slow, which is acceptable.LVMhas been chosen as it allows to growfile systemwithout any downtime. – NarūnasK Nov 14 '16 at 11:26