Hey Strahil,
seems you're the go-to-guy with pretty much all my issues. I thank you
for this and your continued support. Much appreciated.
200mb/reads however seems like a broken config or malfunctioning gluster
than requiring performance tweaks. I enabled profiling so I have real
life data available. But seriously even without tweaks I would like
(need) 4 times those numbers, 800mb write speed is okay'ish, given the
fact that 10gbit backbone can be the limiting factor.
We are running BigCouch/CouchDB Applications that really really need IO.
Not in throughput but in response times. 200mb/s is just way off.
It feels as gluster can/should do more, natively.
-Chris.
On 24/03/2020 06:17, Strahil Nikolov wrote:
Hey Chris,,
You got some options.
1. To speedup the reads in HCI - you can use the option :
cluster.choose-local: on
2. You can adjust the server and client event-threads
3. You can use NFS Ganesha (which connects to all servers via libgfapi) as a
NFS Server.
In such case you have to use some clustering like ctdb or pacemaker.
Note:disable cluster.choose-local if you use this one
4 You can try the built-in NFS , although it's deprecated (NFS Ganesha is fully
supported)
5. Create a gluster profile during the tests. I have seen numerous improperly
selected tests -> so test with real-world workload. Synthetic tests are not
good.
Best Regards,
Strahil Nikolov
--
with kind regards,
mit freundlichen Gruessen,
Christian Reiss
_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/privacy-policy.html
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/YOVAMJAWUFLJY6XNXQDURPWISKLSMAOZ/
