http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02964959/c02964959.pdf
Issue
Although using a filesystem is necessary for most storage deployments, it involves additional work to access
the data stored on the IO Accelerator. These additional lookups decrease maximum system performance
when compared to the benchmark results achieved by benchmarking directly on the block device.
Solution
When you are running micro-benchmarks to vet system performance, you should benchmark by accessing
the block device directly. Otherwise, use any application-native filesystem implementation, possibly testing a
handful where available. HP testing has shown XFS to be reasonably fast under most circumstances. For
Linux, HP recommends using the XFS filesystem.
Webinar: Testing High-Performance Vector Search With CatBench on Google
AlloyDB Omni
-
TL;DR: I’m doing a CatBench Vector Search on AlloyDB webinar (hacking
session style!) with Google on Wednesday, July 23th at 9am EDT. I was
having some cha...
Acum o zi
Niciun comentariu:
Trimiteți un comentariu