This documentation is for a release that is no longer maintained
See documentation for the latest supported version 3 or the latest supported version 4.Questo contenuto non è disponibile nella lingua selezionata.
Chapter 14. Optimizing On GlusterFS Storage
14.1. converged mode Guidance for Databases Copia collegamentoCollegamento copiato negli appunti!
When you use converged mode for applications, follow the guidance and best practices provided in this topic so that you can make informed choices between gluster-block and GlusterFS modes based on your type of workload.
14.2. Tested Applications Copia collegamentoCollegamento copiato negli appunti!
In OpenShift Container Platform 3.10, extensive testing was done with these (no)SQL databases:
- Postgresql SQL v9.6
- MongoDB noSQL v3.2
The storage for these databases originated from a converged mode storage cluster.
For Postgresql SQL benchmarking pgbench was used for database benchmarking. For MongoDB noSQL benchmarking YCSB Yahoo! Cloud Serving Benchmark was used for benchmarking and workloada,workloadb,workloadf were tested
14.3. Support Matrix Copia collegamentoCollegamento copiato negli appunti!
Database | Storage backend: GlusterFS | Turn off Performance Translators | Turn on Performance Translators |
Postgresql SQL | Yes |
|
|
MongoDB noSQL | Yes |
|
|
Database | Storage backend: gluster-block |
Postgresql | Yes |
MongoDB | Yes |
The performance translators for GlusterFS, as mentioned above, are already part of the database profile delivered with the latest converged mode images.
14.4. Test Results Copia collegamentoCollegamento copiato negli appunti!
For Postgresql SQL databases, GlusterFS and gluster-block showed approximately the same performance results. For MongoDB noSQL databases, gluster-block performed better. Therefore, use gluster-block based storage for MongoDB noSQL databases.