You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, sorry, it seems I missed your issue, as well as several more :-)
I have no idea about AWS, haven't checked Vitastor there. :-)
First you should benchmark the raw disks with fio. Then, if they have write-back cache (i.e. based on consumer NVMes without capacitors) you should add --disable_data_fsync false during vitastor-disk prepare. Then you should also check the network latency.
These are basic things which amount to the performance of a cluster. Theoretical performance is described here https://git.yourcmc.ru/vitalif/vitastor/src/branch/master/docs/performance/theoretical.en.md
We can benchmark it on AWS if you really want and if you give me ssh access :)
👋 Quick question, what's the expected performance using Vitastor in AWS with local NVMEs?
For instance, using d3en.xlarge instances I get this numbers:
which is slow.
OS: Debian 12 - no changes
Kernel: 6.1.0-10-cloud-amd64
do I need to tune sysctl?
Thanks!
The text was updated successfully, but these errors were encountered: